Users
Settings, Users (/admin/users), gated by the user.manage permission.
A user is somebody who signs in to the technician console. Almost always ICT staff.
A person is a student, staff member or parent, synced from your directory or student information system. People do not sign in to the console. They tap a card at the kiosk or sign in to a portal.
You manage users here. People are managed by the connectors that sync them, and viewed under people.
Creating an account
Section titled “Creating an account”Press Add user and give a name, an email address and one or more roles. Build your roles first. Creating twelve accounts and then discovering the role is wrong means fixing twelve accounts.
Two accounts cannot share an email address. Adding a second one is refused with “An account with that email address already exists.”
How they sign in
Section titled “How they sign in”Under How they sign in, choose one:
| Choice | What happens |
|---|---|
| Email them a link to set their password | They get a link that works once, for 72 hours, and choose their own password. Nobody else ever knows it |
| Set a password now | You type a password of at least 14 characters, not a common one, and tell them privately. They can change it after signing in |
| Sign in with your provider | No password. They use their school account through single sign-on |
The emailed link is chosen for you when the school can send email. Single sign-on is offered only when it is on and covers the address’s domain, and it is then the default. If the address is not on one of the school’s staff or single sign-on domains, a warning asks you to check it, because whoever reads that inbox gets the account and its roles.
With the link chosen, the button reads Add and send invite, and the footer says where the link goes.
When email is not available
Section titled “When email is not available”If the school has no working email, or the email fails, the account is still created and the link is handed to you instead, once. Copy it with Copy invite link and send it to them yourself, then press I’ve sent it. The dialog asks before it closes if you have not copied the link, because it cannot be shown again.
Invites in the list
Section titled “Invites in the list”Until the person sets their password, their status reads Invited · expires with the date, or Invite expired once the link has lapsed.
Open the account to see the Invite section, which says where the link went and whether it still works:
- Resend invite sends a fresh link and stops the old one. It asks you to confirm it is you. After an invite is cancelled, the same button reads Send invite.
- Cancel invite stops the link after a confirmation. You can send another later.
An invite is only for an account that has never signed in. It also stops working when the account is deactivated (by hand or through SCIM) or when somebody sets its password by hand.
What the person sees
Section titled “What the person sees”The link opens a page with the school’s name and branding, made for a phone. It names the account it is for, asks twice for a password that meets the staff password rule (at least 14 characters, not a common one, and not their address or the school’s name), and says when the link stops working. After Set password they go to sign-in with their address already filled in. A link that has expired or was already used says so, and tells them to ask the ICT team for another.
If the account holds administrator-level access, the person is asked to set up two-factor authentication after their first sign-in, whatever the school’s two-factor policy.
The invite email is the Staff invite message under email messages. It cannot be switched off.
Limits
Section titled “Limits”- A link works once and lasts 72 hours. Each account has at most one live invite.
- Resending is limited to 5 an hour for one address and 50 an hour for the whole school.
- The invite page itself is rate limited, and an unknown, expired, cancelled or used link all give the same answer, so a link cannot be guessed.
- Plugboard keeps only a fingerprint of each link, never the link itself.
- Adding, resending, cancelling and accepting an invite are each recorded in the audit log.
Confirming it is you
Section titled “Confirming it is you”Creating, editing or deleting an account, resetting somebody’s password, signing them out everywhere, or changing which campuses they administer asks you to confirm it is you before it runs. Answer with a code from your authenticator, a passkey, or your password, whichever your account has.
This guards against a laptop left unlocked and signed in while you are at somebody’s desk. The confirmation lasts for that one action, not for the session.
What an account carries
Section titled “What an account carries”| Field | Notes |
|---|---|
| Name | Shown on assignments, in the audit log and on notes |
| The sign-in identifier, and where notifications go | |
| Roles | One or more. Permissions are the union of them |
| Active | Deactivating blocks sign-in without deleting history |
| Two-factor | Set up by the user themselves under Account |
Deactivating rather than deleting
Section titled “Deactivating rather than deleting”Deactivate somebody who has left. Their history stays attached to their name, so “who closed this repair in 2024” still has an answer.
Deleting an account that has done work leaves records pointing at nobody. The screen discourages it for that reason.
Deactivation takes effect immediately and revokes their refresh tokens, so they are signed out rather than remaining signed in until their session expires.
Automating the leaver problem
Section titled “Automating the leaver problem”Turn on SCIM provisioning and your identity provider pushes the change the moment HR disables the account, revoking every refresh token in the same transaction.
Single sign-on and fallback passwords
Section titled “Single sign-on and fallback passwords”With SSO configured, staff sign in with Entra or Google instead of a local password.
Keep at least one administrator with a fallback password set on their account, so an identity provider outage does not take your service desk with it. Setting it in advance saves somebody having to reach a terminal.
Users set their own fallback password under Account.
If you did not do this and everyone is locked out, a self-hosted deployment
still has a way back: plugboard admin-reset, run on the machine itself. See
nobody can sign in. On
managed hosting, ask [email protected].
Two-factor authentication
Section titled “Two-factor authentication”Users set up TOTP themselves under Account. Scan the code with an authenticator and confirm a six-digit code. Who must set it up is the school’s choice, under sign-in security; a fresh school asks it of administrators.
Turn it on for your own account before you invite anyone else. The account with every permission should be the best-protected one.
Who can do what
Section titled “Who can do what”Permissions come from roles, and the same permissions apply everywhere. The web interface, the public API, the MCP server and Ask all run the same checks. A user cannot do through chat or through an API key what their role forbids.
Each account shows its seat in the list and on its record: Technical, Business or Participant (free). The seat follows from the roles the account holds; nobody chooses it by hand. When a role you are granting would raise someone’s seat, the role step says so, for example “This makes Sam a Technical seat.” It never stops the grant. See seat types for which permissions make which seat.
On a licence priced per student, every staff account is included: seats are counted, never priced, and the role step names the seat and nothing more.
An earlier licence on the one plan includes 2 Technical seats and prices Business seats as needed. There the role step adds the count, for example “This makes Sam a Technical seat, 3 of 2 included.” Going over is settled at renewal rather than blocking anything, so hiring a technician never locks the desk. A seat type the licence does not price raises no count and no warning.
Seat counts are reported as part of the count-only telemetry a deployment sends.