Sign in customers and citizens to your apps
Let people who are not members of your organization, such as customers or citizens, sign in to chosen apps by emailed code or passkey. Each organization sees a different identifier for them, and they can delete their sign-in at any time.
By default, an app your organization registers signs in only your organization's members. You can also open an app to end users: people outside your organization, such as the customers of a support site or the citizens using a permit portal. End users sign up at the app itself. They never become members, never see the Scrydon platform or a workspace, and are never sent to your downstream apps by provisioning.
Open an app to end users
Under Settings → Organization → Apps → your app → Access, set Who can sign in to Members and end users. This works for OIDC and SAML apps. Only an owner or administrator of the organization can change it, and every change is recorded in the audit log.
A Microsoft Entra SAML app always signs in members only, because Entra federates your organization's own tenant.
The member assignment you set on the app (all members, or the people and teams you choose) still applies to members. End users are admitted next to it.
How an end user signs up
- The person opens your app and is sent to Scrydon to sign in.
- They enter their email address and the code Scrydon emails them.
- Scrydon creates their account and sends them back to your app.
No password is ever set. After signing up, the person can add a passkey. A SAML app admits end users who already have an account. Signing up starts at an OIDC app.
An address that already belongs to one of your members cannot also be an end user. A person who is both needs a separate address for each.
What your app receives
Each end user gets a different random identifier at each organization. It
is the sub of the ID token and of userinfo for an OIDC app, and the
persistent NameID for a SAML app. Two organizations cannot match their
records on it. If your app asks for the email or profile scopes, it
receives those values too, and an address is the same everywhere.
Your end-user sign-in policy
The organization policy End-user sign-in sets:
| Setting | Values | Default |
|---|---|---|
| Allowed methods | Emailed code, passkey | Both |
| Minimum strength | Any, two factors, phishing resistant | Any |
| Retention | 1 to 730 days | 365 days |
It is separate from your members' sign-in policy. A sign-in below it is refused, and every refusal of an end user is recorded in the audit log as end-user admission refused.
Retention and deletion
When an end user has not signed in to any of your apps for the retention period, Scrydon deletes their sign-in with your organization. An account left with no sign-in anywhere is deleted with it.
End users can delete their own data at any time from their account page. After signing in, they land on it instead of the platform. They can remove their sign-in with one organization, or delete their whole account. Both need a recent sign-in. Removing a sign-in signs them out of that organization's apps at once, and signing in again gives them a new identifier.