Skip to content
PortalBase

Glossary

Directory sync

Directory sync copies your people list from the company's directory into an app, adding, updating and removing users automatically as the list changes.

Also calleduser provisioning, SCIM, automatic user provisioning, HR sync

What it means

Directory sync links an app to the company's user list. When someone is hired, they appear in the app. When they change role or crew, the app updates. When they leave, they're removed or disabled.

The list usually comes from an identity system or HR system. The app doesn't need someone to type in names or keep a spreadsheet. It follows the source.

Not every company runs a directory, and not every worker is in it. Seasonal and contract crews are often managed outside it. Ask how those people get added, and whether a lead can add them by hand.

Why it matters

The main risk is the person who left months ago and still has an active account. Directory sync closes that gap. It also keeps crew assignments and training lists current without a person updating them by hand.

What it looks like on a site

  • A hire in the company directory shows up in the app, with their role and crew.
  • A person who moves crews is moved in the app, and their assigned training follows.
  • A person who leaves is disabled the same day, without a ticket to each app owner.
  • A lead can add a day laborer by hand when they aren't in the directory.
  • Someone checks the list on a schedule to catch what the sync missed.

This is general information, not legal advice. Check the current rule and your own procedures. Back to the glossary

Common questions

What is the difference between SSO and directory sync?
SSO handles how a person signs in. Directory sync handles who exists in the app and what role they have. Many companies use both.
Why does directory sync matter for offboarding?
When someone leaves, the sync removes or disables their account automatically. That means no old logins stay open in tools nobody checks.