Organizations
Sign-in policies
Allowed sign-in methods, second factor levels, session limits, two-person approvals, and sessions an admin can end.
Built An organization decides what a sign-in to its own apps must prove. The owner or an admin sets the rules in the Console under Sign-in rules → Sign-in and second factor, and an auditor can read them. A saved policy applies at the next sign-in to your apps.
Sign-in policy#
| Rule | Choices | Default |
|---|---|---|
| People may sign in with | Passkey, OpenPulse Authenticator on a phone, single sign-on through your provider, email link | All allowed |
| Require a passkey | A passkey sign-in, whatever else is allowed | Off |
| A session lasts at most | As long as the app keeps it, 8 hours, 12 hours, 1 day, 7 days or 30 days | As long as the app keeps it |
| Devices | Any device, or registered with OpenPulse only | Any device |
A session limit also ends sign-ins that began before you set it: their refresh tokens stop working when the limit is reached. A registered device is one that holds a device key from a CLI or device sign-in.
What a refused person sees#
| Error | Meaning |
|---|---|
org_policy_passkey_required | This organization asks for a passkey sign-in. |
org_policy_method | The way this person signed in is not allowed. The message names the ways that are. |
org_policy_device | This organization asks for a registered device. |
Every refusal is written to the audit log as signin.refused.
Second factor policy#
Set the level a sign-in must reach, for everyone and for single groups. A person needs the strictest level of the organization and their groups. The level is checked when the sign-in finishes, when the code is exchanged and at each refresh, so raising it ends sign-ins that no longer meet it.
| Level | What reaches it |
|---|---|
| No requirement | Any sign-in. |
| Two steps | A passkey or an app approval, or an email link or single sign-on followed by an authenticator or recovery code. |
| AAL2 | A passkey or an app approval. |
| Phishing-resistant | A passkey, or a number-matched approval from a hardware-protected phone key. |
| Passkeys only | A passkey. |
| AAL3 | A passkey bound to one device, such as a security key. |
A grace period of up to 90 days lets people below the level keep signing in while they are asked to add a method. The same page shows who meets the policy and who has no second factor.
Two-person approvals#
The policy can make these admin actions wait for a second admin:
- Removing a member
- Changing a role
- Handing on ownership
- Changing single sign-on
- Creating or revoking a provisioning token
- Revoking a member's device
- Ending a member's session
- Changing the sign-in policy
The second admin decides with their own passkey, and nobody approves their own request. A request waits for one hour. An approval covers that one action on that one target and is spent when it is used.
Sessions#
People → Sessions lists where your active members are signed in: app sign-ins and browser sessions, each with its app, when it started and when it was last used. OpenPulse stores no network address for a session, so none is listed.
| Action | Who |
|---|---|
| Read the list | The owner, an admin or an auditor |
| End one session | The owner or an admin |
| Sign a member out everywhere | The owner or an admin |
An admin cannot end the sessions of the owner or of another admin. An ended session's access tokens are refused at once, and the audit log records session.ended or member.signed_out. A person can belong to several organizations, so you reach only sign-ins to your own apps and realm hosts and those no organization owns.