Identity solutions
Integrate identity systems for cardholder and operator synchronisation.
Command Centre can synchronise Cardholder (and Operator) records with a customer's identity directory, so staff onboarding, offboarding, and access changes flow automatically instead of being entered twice. Four integrations exist, differing by directory and by direction.
On-prem Microsoft AD
Bidirectional (AD↔CC)
v8.20
The workhorse. Major architecture change at v8.50 (XML/certificate to REST API).
Microsoft Entra ID (cloud)
Bidirectional (Entra↔CC)
v9.20
Newest. v1.0 (AD-SSO auth) vs v2.0 (Entra-SSO auth, CC v9.40+).
Nexudus Spaces (coworking)
One-way (Nexudus→CC) + Access events back
v8.30
Team→Access-Group mapping; sends Access Granted events as Check-Ins.
Separately, Active Directory Single Sign-On lets operators log into Command Centre with their Windows/AD credentials. This is an authentication feature, not cardholder sync.
🧭 Where to start
On-prem AD, two-way sync? → Active Directory.
Cloud / Microsoft 365 / Entra tenant? → Entra ID.
Common building blocks
REST API operator + REST Client item. The modern integrations (AD Sync v8.50+, Entra ID Sync) write to Command Centre through the REST API, using a dedicated CC operator whose privileges cover cardholder configuration.
Cardholder Filter / Valid Groups / Valid Containers. Every sync decides which directory users become cardholders, and what happens to a cardholder when they leave the valid scope (leave / deauthorise / remove).
Unique ID mapping. How a directory user is matched to a cardholder (for example Entra Object ID to cardholder External ID, or a unique PDF as a secondary key).
Single Sign-On. AD SSO (and, from CC v9.40, Entra ID SSO) authenticate the person who launches the sync configuration UI.
Last updated
Was this helpful?
