Organization integrations
Open Integrations in the intended organization to connect Cisco Meraki or UniFi. Each card shows its connection status and the actions available to your role.
Cisco Meraki
Section titled “Cisco Meraki”The connection uses Meraki OAuth authorization. Click the connection button on the Meraki card and follow the steps in the Meraki dashboard.
Once connected, you can link a network to a location or use Meraki network import if your plan supports it. LogCentral manages OAuth token renewal.
To remove the connection, see the Meraki disconnection guide.
An Owner clicks Connect UniFi and saves a Site Manager API key. Owners and Members can then open Manage UniFi sites, choose a site and link it to an existing location or create one in the assistant.
The workflow lets you review the collector, authorize detected WAN IPs, activate the location and configure log forwarding. Every change requires an explicit action. Automatic configuration is currently validated on UniFi Network 10.6.109; manual setup remains available for other versions.
Follow Connect UniFi for prerequisites, setup steps and verification of a new received event.
Permissions and limits
Section titled “Permissions and limits”| UniFi action | Owner | Member | Read-only |
|---|---|---|---|
| Connect, replace the key or disconnect | Yes | No | No |
| List sites and manage associations | Yes | Yes | No |
| Configure or restore the destination | Yes | Yes | No |
LogCentral permissions do not replace permissions in the provider account. A site visible in Site Manager may deny access to its console. A location cannot be linked to Meraki and UniFi at the same time.
Unlink all sites before disconnecting UniFi. Restoring a destination, removing an association and deleting a key are separate actions; the UniFi guide explains their effect on log forwarding.
Request another integration
Section titled “Request another integration”Use the integration request card or contact support with the devices and workflow you would like to support.