User management

Purpose: help site administrators add and remove people, fix bad email addresses, and give each person the right level of access.

Who can use this

Organization or facility administrators as defined in your deployment. Teachers without admin rights should ask their lead instead of changing users themselves.

Steps

Open Users (or Team, depending on your build) from the dashboard.
Invite a new person with their work email and the role that matches their job (read-only vs. edit vs. admin).
If someone should not have access anymore, deactivate or remove them per your policy—do not share admin accounts.
When a person’s job changes, update their role the same day so inventory and money-related actions stay auditable.

Expected result

Each active user can sign in and see only the areas their role allows. Inactive users cannot sign in.

What happens next

Permissions for a concise model of who can do what.
System settings for org-wide options that affect every user.

Common problems

Duplicate accounts (two emails for one person) — pick one, merge usage if the product allows, and disable the extra.
“User sees nothing” — check they are assigned to the right facility and a non-guest role.