Every district has jobs that don’t map cleanly onto a generic “Teacher” or “Admin” checkbox: the athletic director who needs to send alerts but shouldn’t touch payments, the communications office that needs the moderation queue but not the whole admin console. ParentSquare and Apptegy both sell custom roles and permission sets. Bloomz adds the same capability, built as a layer on top of the role system already in place, not a replacement for it.
A template, built once
A district admin builds a named role template, Librarian, Athletic Director, Communications Office, whatever your org chart actually has, and assigns it to a specific person at a specific school or department. Build it once, reuse it everywhere that job exists in the district.
Deny always wins
If one person needs almost everything in a template except one thing, an admin can carve out that single exception with an explicit deny, without rebuilding the whole template from scratch. And every template and assignment change is logged, so a permission question six months from now has an answer.
Additive, on purpose
This is a layer on top of Bloomz’s existing role and staff-capability system, not a rebuild of it. That’s a deliberate choice: your district’s existing roles keep working exactly as they do today, and role templates give you a way to grant a specific, reusable set of permissions to a specific job without touching anything else.
Available now, behind a flag
Custom Roles & Permissions is part of Bloomz Complete, off by default until your district turns it on. Learn more on the Insights & Analytics page.