Security settings
Multi-factor authentication (MFA), password and session rules, the sign-in IP allowlist, and who can change them.
- Where
- Admin → Settings → Organization settings → Security · Admin → Roles
- Permission
- Full administrator (sign-in and security policy) · MANAGE_ROLES
- Updated
- October 2026
Overview
Multi-factor authentication (MFA) works with authenticator apps (TOTP), email codes and recovery codes. Text-message codes work where the deployment has an SMS provider configured.
Sensitive actions (role changes, API keys, credential changes) ask people to confirm it's them, unless they signed in within the last 10 minutes.
The security policy sets account lockout, idle timeouts, an absolute session lifetime, password rules and the sign-in IP allowlist.
There are two idle timeouts: one for members, and a shorter one for anyone who can open the admin console.
Sign-in and security policy stay with full administrators, even when MANAGE_SETTINGS is given to someone else.
Custom roles are built from 24 permissions in Admin → Roles.
Single sign-on (SSO) and user provisioning have their own guide. Audit logs, retention and privacy requests are in the Audit section.
Step by step
- 01
Require MFA
Tick Require MFA for workspace users. Everyone then sets up MFA before they can do anything else.
- Methods: an authenticator app, email codes, or text-message codes where an SMS provider is configured
- People already signed in, including the admin who saved the setting, are asked to set it up on their next page load
- Admin → Settings → Organization settings → Security → Require MFA for workspace users
- 02
Set up single sign-on
Connect your identity provider in Admin → Settings → Organization settings → Authentication. Single sign-on & provisioning walks through each provider.
- First, verify the email domain
- Then connect the identity provider and test sign-in
- Once the test passes, require SSO
- 03
Set password and session rules
On the Security tab, choose how failed sign-ins, sessions and passwords are handled.
- Account lockout: failed attempts, the time window and how long the lock lasts
- Idle timeouts: one for members, one for admins
- Absolute session lifetime
- Password rules: minimum length, history, minimum and maximum age
- A password an administrator sets for someone can be changed by its owner straight away
- The minimum age applies only to passwords people choose themselves
- 04
Limit sign-in to your network
On the Security tab, add address ranges to Login IP allowlist. Once any range is set, sign-ins from outside the list are refused.
- Ranges are CIDR blocks, IPv4 or IPv6
- Refused: sign-ins from outside the list, or from an address the server can't determine
- Each refused sign-in is recorded under Security events
- Saving a list that leaves out your own address is refused, so you can't lock yourself out
- 10.0.0.0/8
- 2001:db8::/32
Good to know
- Turn on MFA before you invite the whole company, so everyone sets it up when they first sign in.
- Self-hosted: if the only administrator loses their MFA device and recovery codes, run
reset-mfaon the server. Troubleshooting → Sign-in and single sign-on has the command for each path. - Review refused sign-ins under Admin → Audit logs → Security events, with Failures selected.