Managed accounts and joining
Accounts at a domain your organization verifies come under your organization's sign-in policy after a 14-day notice. Each member has a stable directory id for downstream systems, and people at your domain can join or ask to join.
Once your organization verifies a domain, the accounts at that domain become managed by your organization. That is what lets Scrydon be your organization's identity provider: your sign-in policy applies to your people wherever they sign in.
What a managed account means
For an account at your verified domain, your organization:
- sets how the person signs in. Your organization's sign-in requirement (for example, a passkey) applies whenever they enter any organization in Scrydon, and whenever they sign in to any application through Scrydon. If another organization asks for less, yours still applies. If it asks for more, theirs does.
- closes the email channel for them, if your organization signs in without email codes or password-reset links.
- keeps their address at your domains. A managed person cannot change their email to an address outside your organization's verified domains.
Your organization does not get the person's memberships of other organizations, or any say over what those organizations let them do. Those stay as they were.
When accounts become managed
Scrydon checks every verified domain once a day.
- An account that existed before your domain was verified is told first, in Scrydon and by email, and becomes managed 14 days later.
- An account created after your domain was verified is managed at once.
- A domain on a temporary verification bypass manages no one: only a published DNS record does.
- If your domain lapses or you remove it, its accounts stop being managed.
The notice names your organization, says what it controls and what it does not, and gives the date. Tell your people before you verify a domain, so the notice is not a surprise.
Who may join
Each verified domain has a Who may join setting under Settings → Platform → Identity → Domains:
| Setting | What happens |
|---|---|
| Invitation only (default) | People join only when an owner or admin invites them. |
| May ask to join | A person at the domain can select Ask to join. Owners and admins approve or deny the request in the Join requests list on the same page. |
| Join automatically | A person at the domain joins when they sign in, or when they select Join. |
In every case:
- the person must have verified their email address. An address someone only typed never joins or asks to join;
- they join as a plain member. Give them another role afterwards if they need one;
- a domain on a verification bypass admits no one.
These settings decide who may join, not who may create an account. On a deployment where sign-up is by invitation only, the default, a person at your domain who has no account cannot sign up to join: create the account for them, or invite them.
A person with no organization yet sees the offer on the screen Scrydon shows them after signing in: Join Acme or Ask to join Acme. Nobody else is told which organization owns a domain.
The directory id
Every member has a directory id in your organization: 32 random
characters that never change, whatever happens to the person's name, email or
sign-in name. Downstream systems, such as Microsoft Entra (its
ImmutableID), a SAML application's NameID, or a SCIM directory, use it to
recognize the same person.
- The same person has a different directory id in each organization, so two organizations cannot match their records on it.
- If a member leaves and later rejoins your organization, they get the same directory id back.
- If a person's account is erased, their directory ids are erased with it.
A member can also have a sign-in name (a user principal name such as
jo.smith@example.com) that differs from their contact email. It must be at
a domain your organization has verified, and no two members can share one.
Audit
Each of these is written to the audit log: an account captured or released
(sso.managed_user.*), a change to who may join
(sso.organization_domain.join_policy_changed), a person joining
(sso.domain_join.joined), a join request created, approved or denied
(sso.join_request.*), and a sign-in name change
(sso.directory_identity.sign_in_name_changed).