Create, suspend and offboard accounts
Your organization's owners and admins create accounts at your verified domain, suspend and reactivate them, reset their credentials, and offboard people who leave. A suspended account cannot sign in anywhere.
Once an account is managed by your organization, your owners and admins can act on it the way an identity provider does: create it, block it, make its holder set new credentials, and remove it when they leave.
Who can do what
- Owners and admins of your organization act on accounts your organization manages. For any other account the answer is "not found": another organization learns nothing about it.
- Nobody acts on their own account.
- Only an owner acts on another owner's account.
Every action is written to the Audit Log with who did it and to whom.
Where to find it
- Suspend, reactivate, reset credentials, offboard: open Settings → Organization → Members, select the person, and use the Account block of their detail sheet. The block appears only for an account your organization manages; suspending and offboarding ask you to confirm first.
- Create and import: Settings → Platform → Identity → Domains. Create account and Import CSV appear once a domain is verified by DNS.
Suspend and reactivate
Suspending an account blocks it everywhere, not only in your organization:
- every session it has ends, and it cannot sign in again by any method;
- your organization's apps get no new sign-in, code or ID token for it;
- its OAuth tokens are revoked and its API keys are disabled.
Reactivating lifts the block. API keys stay disabled: create new ones if the person still needs them.
A suspension stays in place if your domain lapses or your organization is deleted. It then can no longer be lifted by your organization; the platform operator lifts it on a written request.
Reset credentials
Remove any of the account's password, passkeys and second factor. Its sessions end. When you reset the password, the holder gets an email with a link to set a new one, unless your sign-in policy closes the email channel.
Offboard
Offboarding is for someone who has left. It suspends the account and removes every password, passkey, second factor and API key. Their memberships of other organizations are not changed, but they cannot sign in to use them.
Create accounts
Create an account for an address at a domain your organization has verified by DNS. The person joins your organization as a member, the account is managed from the start, and they get an email with a link to set their password. An address that already has an account is refused: that account becomes managed through the 14-day notice instead.
To create many at once, import a CSV of up to 500 rows, one email and an
optional name per line, with or without a header line. Each row is created
or refused with its reason.
This works on a deployment where sign-up is by invitation only, the default: an owner or admin opens the account, not the person. Nobody can use it to sign themselves up at your domain.
API
All under the authentication service, for the session's active organization:
| Method and path | Does |
|---|---|
GET /sso-extensions/managed-accounts/:userId | { userId, managed, suspension } |
POST /sso-extensions/managed-accounts | create { email, name } |
POST /sso-extensions/managed-accounts/import | import { csv } |
POST /sso-extensions/managed-accounts/:userId/suspend | suspend |
POST /sso-extensions/managed-accounts/:userId/reactivate | reactivate (409 if not suspended) |
POST /sso-extensions/managed-accounts/:userId/offboard | offboard |
POST /sso-extensions/managed-accounts/:userId/reset-credentials | { credentials: ["password" | "passkeys" | "two_factor"] } |
Errors carry a code: not_managed (404), self_action and
owner_protected (403), not_suspended and account_exists (409),
not_at_verified_domain and import_too_large (400). A suspended account
signing in gets account_suspended (403).
What is not immediate
A suspension takes effect at once for new sign-ins and tokens. Some things already handed out run out on their own:
- a Scrydon page already open keeps its cached session for up to 5 minutes;
- an app that cached a token check keeps it for up to 60 seconds;
- an ID token an app already holds is valid for up to 10 hours. An app that keeps its own session from one must check again.