Set your organisation's password policy
This applies to people who sign in to AtmanID with a password. People who sign in with single sign-on (Okta, Entra ID and others) keep their password with their identity provider and are not affected.
Who can change it: Tenant Owner, PAM Admin and Super Admin. Every change is recorded in the audit log.
How AtmanID approaches passwords
The policy follows NIST SP 800-63B (revision 4):
- Length is the requirement. A few unrelated words make a password that is long, strong and easy to remember.
- No composition rules. AtmanID does not require “an uppercase letter and a number” — those rules push people towards predictable patterns.
- Breached passwords are always refused. A new password is checked against known data breaches without the password ever leaving AtmanID in a usable form.
- No scheduled expiry. Nobody is asked to change a password just because time has passed.
Rolling out (October 2026). While this policy is being introduced, the earlier rules — at least 8 characters, with an uppercase letter and a number — still apply alongside it. The change and reset pages always show the rules that apply right now.
Set the policy
Open Platform Config → Authentication, choose the Session policy tab, and scroll to Password policy.
| Setting | What it does | Lowest allowed |
|---|---|---|
| Minimum length | For people whose role does not require MFA (the password is their only factor) | 15 |
| Minimum length with MFA | For people whose role requires MFA | 8 |
| Refuse passwords that contain names | Refuses passwords containing the person’s name, the name part of their email address, or your organisation’s name | — |
Passwords can be up to 64 characters. You can raise the minimums but not set them below the platform floor. Click Save password policy.
When it takes effect
A policy applies the next time each person sets a password — when they change it, reset it, or set their first password. Existing passwords keep working; nobody is locked out.
The change and reset pages show each person the requirements that apply to them before they type, with a live character count.
Require a change at next sign-in
If you need everyone to move to the new policy now, click Require a change at next sign-in…. The confirmation shows how many people sign in with a password. Each of them chooses a new password, meeting the current policy, the next time they sign in. Nobody is signed out at that moment, and single sign-on users are not affected.
Related
- Require MFA and track enrollment — the MFA requirement also decides which minimum length applies
- Navigate the audit trail — find
PASSWORD_POLICY_UPDATEDandPASSWORD_CHANGE_REQUIRED_BULKentries
© AtmanID · Privacy