Sign-in security
From 1.20.27, Settings → Sign-in security holds the workspace’s own
sign-in rules. It needs Change workspace settings
(workspace.settings_manage), which the Administrator role has. It is in
every edition. Single sign-on, SSO only and break-glass accounts stay
on Single sign-on.
The page has three cards: Require two-step sign-in, Session
lifetime, and API tokens and app connections. Save saves the
first two. Each change is in the audit log as
Updated sign-in security (settings.sign_in_security).
Require two-step sign-in
Section titled “Require two-step sign-in”Who must enter a code from an authenticator app when they sign in with a password. Choose one:
| Choice | Who it covers |
|---|---|
| Nobody (the default) | No one. Two-step sign-in stays optional: each person can turn it on under Account → Security. |
| Administrators | People who can administer users or workspace settings. |
| Administrators and desk agents | Administrators, and anyone who works the desk or reads its reports. |
| Everyone | Every account that signs in with a password. |
“Administrators” means anyone with the Administrator role, or any custom role that can change accounts, roles, workspace settings or single sign-on.
What happens to someone it covers. If they have no authenticator set
up yet, their next password sign-in takes them to Set up two-step
sign-in: they scan a QR code, enter the code their app shows, and save
eight recovery codes. Until they finish, they can use nothing else. Pages
send them back to that step, and the API answers 403 with
code: "two_step_required". Once it is set up, they can’t turn it off
under Account → Security. If someone loses their authenticator, reset
it for them under Settings → Users → ⋯ → Reset 2FA….
What it doesn’t ask.
- Single sign-on sign-ins. Your identity provider brings its own second step.
- Sessions a Duo check approved. Duo counts as the second step. A session let in while Duo couldn’t be reached is asked.
- Sessions opened before 1.20.27. They are asked at their next password sign-in.
Older API tokens. A personal API token that never expires (one made before 1.20.27, or by a settings administrator) stops working while its owner is covered and has no authenticator. It works again once they set one up. Tokens that expire were made by a session that already had to pass the rule.
Session lifetime
Section titled “Session lifetime”However active it is, a session ends this many days after it began, and its owner signs in again. Days a session lasts takes 1 to 90. The default is 30.
The idle timeout (Settings → Workspace → Content) still applies within it. Before 1.20.27 there was only the idle timeout, so a desk tab left open and polling could keep a session going for ever.
API tokens and app connections
Section titled “API tokens and app connections”A list of every account’s personal API tokens and the apps (like Claude) people have connected through the Claude connector. Each acts as its owner until it expires or is revoked. For each one it shows the Person, the Token or app, when it was Last used, and when it Expires: a date, No expiry, or Expired. Filter by person or name narrows a long list.
Revoke (a token) or Disconnect (an app) ends it at once. It needs
Change a user’s role (user.update_role), the permission a password
reset needs. An administrator can revoke anyone’s;
anyone else only the tokens of people whose role is below theirs. Each
one is in the audit log as Revoked an API token or app connection
(user.credential_revoked), against the account it belonged to.
A password reset or a password change revokes all of the account’s own tokens and app connections without anyone visiting this page. See Passwords & API tokens.
Related
Section titled “Related”- Security & encryption: passwords, sessions, throttling and what the server does for you.
- Your account & security: what each person sees.
- Single sign-on: SSO only and break-glass accounts.
