Skip to main content
Identity and directory

Directory sync (SCIM) integration

When someone is removed in Directory sync (SCIM), the security side should hear about it too. That is the point of connecting it. Managed, runs this for you.

Available on requestIdentity and directory
Directory sync (SCIM)ManagedDoors and badges
Illustration of how the connection fits together.

About Directory sync (SCIM)

SCIM is the standard way identity providers such as Okta and Microsoft Entra ID send user and group changes to other systems.

If it is where people are added and removed, it is a sensible source for who should have a badge.

Where it stands today

The Directory sync (SCIM) connection is not switched on by default. If you need it, request it and our team builds the connection for your setup, tests it with you and confirms the scope in your proposal before anything goes live.

What it connects

People and groups, so they line up with who has access.

In the integrations list: Connect Okta, Entra or another identity provider so people who leave lose access.

What Managed does with it

  • Groups are mapped to door groups during setup, agreed with you.
  • Each access change is approved by a person before it happens.
  • Changes are recorded in the Managed customer portal.
About AccessOps

How it gets set up

  1. 01

    We talk through how you use Directory sync (SCIM) and what should happen.

  2. 02

    The Managed team sets up the connection with you and checks it before anything changes.

  3. 03

    The connection and its scope are confirmed in your proposal.

Available on request means our team builds and checks the connection with you once you ask. Labels match the integrations list.

Tell us what you are running today.

The old panel, the NVR in the closet, the badge list nobody wants to own. We will tell you what can connect and what it would cost to run.