Skip to main content

​
The page

At /settings/connections (linked from the sidebar as “Integrations”; the page itself is titled Systems with the strap-line “Add, edit or remove connections”), each connected integration shows as a card: Systems page with cards for Azure AD, Crowdstrike, Duo, Jamf, Lansweeper Scans — each showing the integration name, Features provided icons, last synced time, and (where applicable) a CONNECTED badge

​
Page-level controls

  • AWS Account / IP Whitelist Info (top — small i-in-circle) — opens a dialog listing egress IP ranges for firewall whitelisting
  • Search systems… — filter the card list by integration name
  • Filters — narrow by status / category / feature

​
Feature icons (after “Features provided”)

Each integration declares which Protect features it contributes to: A CrowdStrike card with all four icons confirms it feeds device, Vitals, software, and mobile data. A Duo card with only the person icon confirms it’s identity-only.

​
Connecting a new integration

1

Find the integration

Use the search box at the top of the page.
2

Click the card

A connect / configure flow opens. The exact flow depends on the integration’s authentication model — OAuth, API key, basic auth, or PowerShell relay.
3

Provide credentials

See the integration-specific guide in the Connection Guides tab for the exact fields.
4

(Optional) configure Vitals

For integrations that contribute to Vitals (the signal icon), use the column-gear in Devices to set per-tag requirements. See Vitals Configuration.
5

Wait for first sync

Initial sync can take 15-60 minutes. Watch the Last synced timestamp.

​
Modifying an existing integration

Click any CONNECTED card to open the integration detail page:
  • View sync history (last 10 runs with success/failure)
  • Test the connection (forces a fresh API call without waiting for the next scheduled sync)
  • Update credentials
  • Configure feature toggles (which data types to pull)
  • Pause the integration (stops syncs without deleting it)
  • Disconnect (removes the integration and clears its data after a grace period)
  • Sync Now — trigger an immediate refresh

​
Health & alerts

Stale or broken integrations are surfaced in three places: Best practice: set a Continuous Action that emails when any integration’s last sync is > 24 hours old.

​
Multi-tenancy

For integrations that support multiple tenants (Azure AD with multiple directories, CrowdStrike with multiple instances), click the connected card → Modify → toggle Multi-Tenant. See Multi-Tenancy.

​
See also

Integrations overview

Concepts and category catalogue

PowerShell Relay

For on-prem integrations

Connection Guides

Step-by-step per vendor