Sign-in security
Settings, Security (/admin/security), gated by the user.manage
permission.
Everything on this page applies to everyone at your school, not to your own account. Your own authenticator app, passkeys and password are under your account.
Saving a change
Section titled “Saving a change”Nothing applies as you click. A bar at the foot of the page counts your changes, with Discard and Review changes. The review dialog lists each change with its old and new value and what it does, for example how many people will be asked to set up two-factor before they can use the desk. Save policy then asks you to confirm it is you, and the change is recorded in the audit log as Security policy updated.
Two-factor
Section titled “Two-factor”Who must use it has three choices:
| Choice | Who is asked to set it up |
|---|---|
| Optional | Nobody. Staff may set it up on their own account page |
| Administrators | Anyone who manages users, roles, connectors, backups or billing, wipes a device or reads local admin passwords |
| Everyone | Every staff account |
Administrators carries the Default tag: it is where a fresh school
starts. In permission terms, it covers any account holding *, user.manage,
role.manage, connector.manage, billing.manage, backup.manage,
device.wipe.request, device.wipe.approve or device.laps.read.
Each choice says how many of the people it covers have not set up two-factor. While Administrators or Everyone is chosen and anyone it covers has not, a warning gives the count with a Review users link. Those people are asked to set it up the next time they sign in, and they land on their account page with Set up two-factor sign-in to continue until they do. Tell them first, and keep a tested administrator account with two-factor ready.
The second factor is an authenticator app, or a passkey where the school counts one (see passkeys). Wiping a device, reading a local administrator password and the other sensitive actions ask you to confirm it is you whatever this setting says.
Passwords
Section titled “Passwords”The staff password rule is the same everywhere a staff password is set, and it is not a setting:
- At least 14 characters when nothing else stands behind the password at sign-in, and at least 8 when a second factor does: an authenticator app, or a passkey the school counts as two-factor.
- At most 256 characters, so any passphrase or password manager fits.
- Not a common password. Plugboard carries its own list and checks against
it with no network call. The check ignores case, trims digits and symbols from
either end and undoes the usual letter swaps, so
P@ssw0rd2026!counts aspassword. Digits alone, one character repeated, a repeated word and keyboard or alphabet runs are refused too. - Not the person’s email address, the part before the @, or the school’s name, where the form knows them.
| Where the password is set | Minimum |
|---|---|
| Changing your own password, or your fallback password, on your account | 14, or 8 with an authenticator app or a counted passkey |
| Accepting a staff invite | 14 |
| Add user with Set a password now | 14 |
| An administrator’s Reset password | 14, or 8 if they use an authenticator app |
| A setup link | 14, or 8 with an authenticator app |
The rule applies when a password is set. Existing passwords keep working until they are next changed.
Student and parent portal passwords need at least 8 characters, and are checked against the same common list and the same 256-character limit.
Passkeys
Section titled “Passkeys”Availability:
| Choice | Effect |
|---|---|
| Off | Hidden everywhere. Existing passkeys stop working |
| Available | Staff may register one and sign in with it |
| Required | Staff must register one before they can use the desk |
With passkeys on, three more settings:
- A passkey meets the two-factor requirement. Staff with a passkey are not asked to set up an authenticator app, and are asked for the passkey each time they sign in with a password. It has no effect while two-factor is Optional. Turning it off asks anyone who relied on a passkey to set up an authenticator app.
- Allow passkeys built into the computer. Windows Hello and Touch ID belong to the computer, not the person. Turn it off where technicians share one login; then only security keys and phones can be registered.
- Require a passkey to confirm sensitive actions. Wiping a device or resetting a second factor then accepts only a passkey. Somebody without one confirms registering their first passkey with their password or authenticator code, and cannot perform the rest until they have.
Passkeys are tied to the desk’s web address. If the deployment does not know its own public address, the page says in one line that passkeys need the desk’s web address set and served over HTTPS, with a link to setting the address. It says nothing while the school has passkeys off. Moving the desk to another address stops existing passkeys; passwords and authenticator apps carry on, and staff register again.
Sessions and signing out
Section titled “Sessions and signing out”Sign staff out after a number of minutes idle. A session left unused that long ends, and the person signs in again. Other devices stay signed in.
- 60 is the default for a fresh school.
- 0 turns it off, so sessions are never ended for being idle.
- Anything shorter than the sign-in token’s lifetime acts as that lifetime; the page names it.
- The most it takes is 10,080 minutes, a week.
Network tracking
Section titled “Network tracking”Record where devices were last seen on the network keeps the last access point or switch port for each device. It is off unless you turn it on. Most of those devices belong to students, so this is location information about them: it appears in subject-access exports, goes with an erasure request, and is hidden from students and parents.
Delete sightings after takes 1 to 90 days, 7 by default. A week finds a laptop lost over a weekend without tracing a whole term. Shortening it deletes older sightings at the next clean-up. See network.
Fresh schools and existing ones
Section titled “Fresh schools and existing ones”A fresh school starts with two-factor for administrators and a 60-minute idle sign-out, so the first administrator sets up an authenticator app before the desk opens. A school’s saved policy is never changed by an upgrade: it keeps what it has until an administrator changes it here.
Related
Section titled “Related”- Users, and confirming it is you before sensitive changes.
- Roles and permissions, which decide who counts as an administrator above.
- The security model.