Manage the person’s account
Invite and maintain eligible school accounts, with one assigned role for each account.
Users, roles
& permissions
The right responsibilities. The right information.
Give each person the access their work calls for. Keep account roles, permitted actions and the school records they can reach connected as your team and responsibilities develop.
A role with a clear purpose
Who they are.
What they can do.
Which records they can reach.
Choose the permitted actions
Use the school’s roles or prepare a compatible custom role with the permissions needed for its purpose.
Keep scope connected
Apply school-wide, assigned-campus, class, self or linked-child scope according to the account’s identity and role.
Access that reflects a real responsibility
Shape the role.
Keep the boundaries clear.
A role brings compatible permissions together for its identity and data scope. Use it to make responsibilities understandable when a person joins the school or takes on different work.
- Review the role’s identity type and scope before choosing permissions.
- Select supported actions for the work the role is intended to perform.
- Assign the role and the relevant campus or teaching relationships through the school’s access workflow.
The action and the records belong together
One school.
Several meaningful scopes.
The role’s identity determines the compatible scope. Assignments and verified relationships then give that scope its school context.
Across the school.
Permitted actions can reach school-wide information through an organisation scope.
Assigned campuses.
Staff work within the campuses assigned to their account and the actions their role permits.
Assigned teaching.
Teaching relationships define the classes and course information available to the teacher.
Their own learning.
A student’s self scope connects the account to its own school and learning records.
Verified child links.
A linked-child scope follows the verified relationship and information grants for each child.
For your team
Access that supports
the work people are trusted to do.
Founders & authorised administrators
Keep responsibilities understandable.
Maintain people and roles using the account-management authority available to your role.
School & branch administrators
Work within the local context.
Use permitted actions in the campuses assigned to your staff account.
Teachers, students & families
Reach the relevant information.
Use the teaching assignment, student identity or verified child relationship connected to the account.
Planning useful access
How do roles, scopes and protected settings work?
Understand the relationship between an account, its role and the school information available to it.
Can we create roles for our own school responsibilities?
Yes. Custom roles combine compatible permissions with a supported identity and scope. Staff can use school-wide or assigned-campus scope, teachers use assigned classes, students use self scope and parents use linked-child scope.
Can an account have more than one role?
Each account has one assigned role. Its permissions work alongside the relevant campus, teaching, enrolment or guardian relationships, so access reflects the actual responsibility and context.
Can every role and ownership setting be changed?
Founder and full-access settings are protected. A staff administrator cannot transfer Founder ownership by changing an account’s role, and permission grants remain limited by the administrator’s own authority.
Does a reporting permission replace a reporting assignment?
Academic reporting also checks the assigned preparation, review or publication responsibility and the relevant reporting scope. Give the person the required authority and the appropriate reporting assignment for the work they will perform.
Keep exploring
One school. More connected possibilities.
Users, roles & permissions
Make school access a clear part of each responsibility.
Connect the person, permitted actions and the records their work requires.