Skip to content
Dashboard
Theme
Theme

Out-of-domain users

How users whose email is outside the organization's verified domains are stored but flagged out_of_domain and not emitted as provisionable.

View Markdown

Directory users outside their organization’s verified email domains are stored with state=out_of_domain. They appear in management reads but are not emitted as provisionable users. Membership events for such users are also suppressed.

Do not provision access just because a stored SCIM user exists. Respect the normalized state and your application’s tenant policy.

When an existing in-domain user moves outside the verified domains, the core emits membership removals followed by dsync.user.deleted with reason=out_of_domain. Revoke that user’s local access and sessions as you would for another deprovisioning event. If the user returns to an allowed domain, created and membership-addition events rebuild its provisionable state.

Domain verification belongs to an organization in one environment. An admin must verify the proper DNS domain; adding an email string to your application’s allow-list does not replace that check.

See directory events and session revocation.