# Configure Directory Sync

Directory sync brings organization membership or group information from the
configured identity system. It requires administrator access and deployment
support for the identity integration.

![Directory, team, and resource access: A synced group does not automatically establish access to every resource.](/screenshots/current/directory-access.svg)

## Keep One Owner for Membership

Directory sync is useful when your identity system already owns groups and membership. Group mappings let that organization structure inform Redbelt teams instead of maintaining two unrelated member lists.

Check the intended group and its members, not just the group’s name. A successful directory sync does not share every file with that group. Review team mappings and resource access separately, and follow the provider-owned path for values managed by the directory.

## Set up and inspect

1. Open **Settings → Organization**.
2. Under **Identity and security**, find **Directory Sync** and click **Manage**.
3. Use **Configure Directory Sync** to open the offered provider setup.
4. Complete the administrator configuration for the intended organization.
5. Return to Redbelt and inspect connection status and **Synced Groups**.

Do not configure an unrelated directory simply because it is already signed in
in the browser. Confirm the organization and intended provisioning scope before
enabling group or member synchronization.

## Review group mappings

Inspect how synced groups correspond to Redbelt teams. For a launch team, check
the specific group membership rather than relying on a similarly named group.
Treat directory-managed values as provider-owned unless the UI explicitly offers
a supported local override.

## Check changes

After a provider-side membership change, inspect the sync state and resulting
Redbelt membership. Syncing a group does not establish access to every document;
review team sharing separately.

If groups are missing or stale, check provider connection health, selected scope,
and synchronization status. Escalate failed identity configuration to the
deployment administrator rather than duplicating directory-managed users manually.

Related: [members and teams](/admin/members/), [roles](/admin/roles/), and
[sharing](/knowledge/sharing/).
