Every account,one place.

The roster is one table: everyone in the organization, what plan they are on, which department and tags they carry, and when their access ends. Adding a cohort is a file, not an afternoon — and you see exactly what will be created before anything is.

• Bulk import with a preview first

  Upload the list, check the rows it parsed and the count it will create, and only then commit. Nothing is written while you are still reading it.

• Plans and expiry per person

  Set who is on which plan and when their access ends, so a cohort that finishes in June stops in June without anyone chasing it.

• Reset a password without a support ticket

  Someone is locked out ten minutes before a lesson. Reset it from the roster and carry on.

• Disable rather than delete

  Take access away when someone leaves while their record and history stay intact for as long as you need them.

Handing an AI to a few hundred students means someone will eventually ask what one of them typed into it. Administrators can open a person, see their conversations, and read the one that matters — so the answer takes a minute instead of a week and a policy meeting.

• Open a person, see their conversations

  Their chats are listed by title. Pick one and the messages open beside it.

• Built for the incident, not for browsing

  It exists so a safeguarding question has an answer. Tell your community it is there — that honesty is the point of having it.

• The record survives the account

  History stays readable after someone is disabled, which is usually exactly when it is needed.

Nobody thinks in user IDs. They think in Year 8, in the science department, in the pilot group. Tags let the roster match how people already describe each other, so finding the right forty accounts is a filter rather than a search.

• Make the tags you actually use

  Class, subject, year, campus, pilot cohort. Name them yourself rather than fitting into a fixed hierarchy.

• More than one at a time

  A teacher can be science and Year 8 and pilot group at once, because they are.

• Tag a whole selection in one go

  Select the rows, apply the tag. Onboarding a cohort does not mean opening forty records.

• Filter the roster by any of them

  Narrow to a tag or a department and act on exactly that group.