Skip to main content

Teachers

Who this is for: directors · Where: Teachers in the sidebar.

What this page is for

Your teaching staff: who has an account, who has been invited but not joined yet, and how much of the school's AI budget each one may spend.

Inviting a teacher

Enter their email address and send. They receive a link that creates their account and joins them to your school with the teacher role.

The invited teacher can accept in one of two ways:

  • Sign in with Google, or
  • Set an email and password on the invitation page.
The invitation proves the address

The account is created already confirmed. Opening a tokenised link sent to that mailbox is the same proof of ownership a confirmation email would give, so a second round-trip would add nothing.

The list of pending invitations updates by itself when someone accepts — you do not need to refresh.

Revoking an invitation

Revoke it and the link stops working. The revoked row stays visible for about a minute as confirmation, then disappears on its own. That is deliberate: an invitation that vanished the instant you clicked would leave you unsure whether the click registered.

Only pending invitations are listed. Accepted and expired ones are not clutter you need to see.

The token pool

Every AI action a teacher takes — generating an exam, a lesson plan, a presentation — spends tokens from your school's monthly pool.

The page shows:

  • Pool — the school's monthly budget
  • Allocated — the sum handed out to teachers
  • Used — what has been spent this period
  • Unallocated — what is still free to give out

Set a per-teacher budget by editing the number on their row.

Two limits you will hit

You cannot allocate more than the pool holds. The sum across all teachers must fit inside the school's monthly budget. Trying to exceed it is rejected rather than silently clamped, so you always know it did not apply.

You cannot set a budget below what that teacher has already used. If a teacher has spent 40,000 this month, 30,000 is refused. Their spend already happened — a budget under it would be fiction.

The pool moves on its own when pupils pay

The school budget is derived from paid pupils. When a subscription lapses the pool shrinks, and if allocations no longer fit, every teacher's allocation is scaled down proportionally to make them fit again.

Tokens already used are never touched by this — only the ceiling. If a teacher reports a budget they did not set themselves, this is why.

Rules and limits

  • Directors only.
  • Invitations: one email each; revocable; pending ones listed only.
  • Allocations must fit the pool and must not fall below tokens already used.
  • The pool follows paid pupils and can shrink; allocations rescale proportionally.
  • Teachers can also buy a personal top-up, which is theirs and is not part of your pool.

Troubleshooting

"Saving an allocation fails." Either the total would exceed the pool, or the number is below what that teacher already spent. Both are refusals, not glitches.

"A teacher says they are out of tokens but I gave them plenty." Check the pool. If pupil subscriptions lapsed, allocations were rescaled down.

"The invited teacher never got the email." Ask them to check spam. If it never arrives, revoke and re-send — the link is what matters, not the message.

"An invitation disappeared." It was accepted, expired, or revoked. Accepted teachers are in the main list.

"I want to remove a teacher." Deactivate them from the list. Their authored work — lesson plans, exams — is not deleted with them.