# Directory Integrations

Directory integrations connect Incode to your organization's user directory, syncing employee records so that Incode can look up users and perform claims matching during verification sessions.

When a directory integration is configured, Incode can locate a user by their `loginHint`—typically a corporate email address or employee ID—and match verified identity attributes from their government-issued ID against the data in your directory. This ensures that the person completing a verification is the same person on record.

Directory integrations do not require a linked Workflow and do not trigger verification sessions on their own. They supply the user data that other integration types—such as IAM, ITSM, and Custom—rely on when performing directory-backed lookups.

Directory integrations also populate the **Directory Information** page in Dashboard, which lists all synced users and their enrollment status.

<IntegrationsEnablement />

***

## Understand Directory Sync

After a directory integration is configured and connected:

1. **Incode pulls your user records** from the connected directory, Okta or Microsoft Entra, and stores the relevant identity attributes: name, email, employee ID, and any mapped claims fields.
2. **Records stay in sync**. User additions, updates, and deactivations in your directory are reflected in Incode automatically.
3. **A verification session starts**. Incode uses the `loginHint` to look up the user's directory record and supply their attributes to the claims matching module.
4. **Claims matching runs**. Verified attributes from the government-issued ID (name, date of birth, address, email, phone) are compared against the directory record. Mismatches can be configured to trigger a hard stop or a soft flag for manual review.

> 📘 **Note**
>
> Directory sync is a prerequisite for claims matching in IAM, ITSM, and Custom integration flows. Configure your directory integration before setting up dependent integration types.

***

## Available Directory Integrations

<DirectoryIntegrations />

***

## Directory vs. IAM Integrations

Directory and IAM integrations both involve Okta and Microsoft Entra, but they serve different purposes:

- **Directory integrations** handle user data sync. They tell Incode who your users are and what attributes they have.
- **IAM integrations** handle authentication flows. They trigger verification sessions when a user signs in, resets credentials, or requires a higher-assurance check.

A directory integration is typically a prerequisite for IAM and other integration types that rely on claims matching. The<br />[IAM integrations](https://developer.incode.com/docs/iam-integrations) page lists authentication-layer counterparts.