School accounts do not use individual Free/Pro/Max plans.

Instead, the school admin controls shared chat pools and studio assignment budgets for teachers and students.

The admin workflow

School Users → School Top-up → School Assign │ │ │ roster & buy bonus set per-user defaults pool packs caps & bonuses 

1. Users — see every teacher/student, their caps, and usage.
2. Top-up — purchase image and video bonus pool packs (Usage tab).
3. Assign — raise individual caps from the pool budget (inline edit or bulk).

Chat pools are configured separately on the Users tab (teacher vs student shared limits).

Default per-user studio caps (plan base)

Every assignable school member gets a plan-base floor built into their cap:

These defaults are not editable by school admins (only Zense can change the platform default). Admins assign bonus credits above this floor.

Chat defaults (configurable per school):

Assignment budget formula

ceiling = (assignable members × plan base per seat) + bonus pool 

Image example — 50 students, 10 teachers, 0 bonus pool:

• Plan base capacity = 60 × 100 = 6,000 image credits assignable
• Admin can distribute school-funded caps up to 6,000 total across members

Video example — same 60 members, 0 bonus:

• Plan base capacity = 60 × 200 = 12,000 video credits assignable

With bonus pool — buying 2 image packs adds 2,000 bonus credits:

• Image ceiling = 6,000 + 2,000 = 8,000

School top-up (bonus pools)

Admins buy pool packs from School Management → Usage:

Each pack is worth 10× an individual 100-credit top-up — designed for whole-school purchases. Quantity 1–30 packs per checkout.

Bonus pool credits are unassigned until you raise user caps. The Usage tab shows:

• Bonus pool — purchased, not yet assigned
• School-funded assigned — already allocated to user caps
• Assignment remaining — still available to assign

School assign (per-user caps)

From Users → Teachers / Students:

Chat pool (role-wide shared limit)

• Set the teacher chat pool or student chat pool total — all members of that role draw from this aggregate limit.
• Set default per-user chat cap for new members / monthly reset (editable).

Image & video caps (per user)

• Each row shows the member's display cap = plan base + school bonus assigned + any personal top-up they bought themselves.
• Click to edit — you can only assign bonus up to assignment remaining.
• Bulk assign — set the same cap for all teachers or all students at once.
• Minimum display cap = plan default + personal top-up (admin cannot go below the member's own floor).

Override users — Zense support may set creditLimitOverride on specific accounts; those users are excluded from the school assignment budget.

How caps compose for one user

Example student after admin assigns extra image credits:

Usage deducts from their used counter; when the monthly reset runs, school-funded portions return to the admin's assigned level (personal top-ups persist).

Chat pools vs studio assignment

Teachers and school admins on the teacher role share the teacher chat pool. Students share the student chat pool.

Monthly reset

• Member usage counters clear.
• Studio caps reset to admin-assigned levels (plan base + bonus assigned).
• Personal studio top-ups remain on the cap.
• Bonus pool unassigned balance carries over.

Chat pool used totals also reset; pool limits stay unless the admin changes them.

Individual top-ups inside a school

Students and teachers can still buy personal image/video top-ups (9 HKD / 19 HKD per 100). Personal top-ups:

• Add to their display cap immediately.
• Are not counted against the school's assignment budget.
• Persist through monthly resets.

Admins see personal top-up totals in the Users table when managing caps.

Quick admin checklist

1. Open School Management → Usage — review chat pool usage and studio assignment bars.
2. Top up image/video bonus pools if assignment remaining is low.
3. Open Users — set default chat caps for each role if needed.
4. Assign studio bonus to individuals or bulk-update a role.
5. Direct members to Settings → Usage to monitor their own usage.

For moderation, join codes, and LLM policies, see School management overview in the School Management collection.