The role catalogue: what can each role actually do?
Goal
This guide answers two questions: "which role do I give this person?" and "what does this role actually mean?". Each role here has a card setting out its real abilities as they stand in the system today, and setting out what it cannot do as well — because some roles are wider or narrower than their names suggest.
There are thirteen built-in roles in the system, and there is no way to create a new one from the interface.
How to read this guide
- A role is a bundle of abilities, not a job. A role's name is shorthand for a particular set of abilities, and it means the same thing at every school.
- The scope decides "where". The role says what the person can do, and the school (the branch) they are assigned to says where they can do it. A person may be SchoolAdmin at one branch and Finance at another.
- Roles combine and do not conflict. If a person holds more than one role at the same school, their abilities are the union of all their roles' abilities; no role cancels another.
- A change does not take effect immediately. Adding or withdrawing a role takes effect when the person's session refreshes or at their next sign-in, not in the session they have open now — and at most 15 minutes, because the session refreshes automatically within that time and needs no sign-out from them. If you want the effect immediately, ask them to sign out and back in.
- Restricting the activity scope is different: it takes effect from the administrator's next request, with no waiting and no sign-out. The detail is in Restricting an administrator to particular activities.
Inside the permissions screen, four groups still carry English headings: Memberships, Imports, Partners and Certificates. Your colleagues using the portal in Arabic see this; you will not.
At a glance: which role for which person?
| Role | Who it is usually for | In one line | Sensitivity |
|---|---|---|---|
| SystemAdmin | The platform's owner | Full access bypassing every check, and it cannot be edited | Very high |
| SchoolAdmin | The school's owner or manager | Everything to do with the branch: activities, registrations, payments, people and reports | Very high |
| ActivityAdmin | The programmes and activities manager | Builds activities and runs registrations completely — with no financial operation at all | High |
| Coordinator | The operational coordinator in the field | Organises activities, groups and attendance, and runs registrations completely — with no financial operation at all | High |
| Cashier | The receptionist who takes the money | A payments desk: takes the payment and records it, with no decision on the request | Medium |
| Finance | The accountant or financial reviewer | Reads and confirms payments only, with no registration decisions | Medium |
| ContentEditor | Whoever writes and publishes the programme descriptions | Authoring and publishing activities only, with no registrations and no attendance | Medium |
| Integrations | The person responsible for exchanging data | Reading activities and registrations and exporting them | Low |
| SupportReadOnly | The support team | Looking at the lists and the dashboard with no changes and no exporting | Low (sees students' names) |
| SupportAgent | The platform's support team, not the school's | Support tickets at every school: triaging and answering | High (crosses the school boundary) |
| ProviderManager | A manager at a company contracted by the school | Runs their own programmes and the children enrolled in them, and sees nothing else of the school | Medium (confined to named activities) |
| Trainer | Whoever stands in front of the children | Attendance, journals and the student roster for their own activities only | Medium |
| Parent | The families | Grants nothing inside the admin portal | Low |
The Choose role list is built according to who opens it. A system administrator sees the thirteen less SystemAdmin, Parent and Trainer — ten of them — and the exclusion is enforced on the server, not only in the interface. A school manager sees nine and can assign all nine: SchoolAdmin, ActivityAdmin, Cashier, ContentEditor, Coordinator, Finance, Integrations, SupportReadOnly and ProviderManager. SupportAgent is not shown to them at all, and only a system administrator may grant it. A trainer is created from the trainers screen, and a guardian is created when they register themselves. The detail is in Adding an administrator with particular permissions.
A card for each role
SystemAdmin
The highest role on the platform: it carries no list of abilities at all, because it bypasses every permission check.
It can: everything at every school, including what no other role holds, such as creating a school, deleting a school, correcting a guardian's email and managing partner integrations. And it is the only one that sees the Reset password button on an administrator's row.
It cannot: nothing inside the system is forbidden to it. But its row in the permissions editor is locked and shows Full access (locked), so its abilities cannot be edited either up or down. And nobody — not even it — can read an existing password; it can only create a new one-time password.
The usual job title: the platform's owner or its technical administrator.
When to choose it over another: do not choose it from the add-admin screen, because it is not available there at all. If what you need is full authority over one branch, the answer is SchoolAdmin, not SystemAdmin. See The system administrator's playbook.
SchoolAdmin
The most comprehensive role within the branch: it holds in practice every school-level ability, which is why — full access appears beside it in the list with an explicit warning.
It can:
- Activities: viewing activities, viewing archived activities, creating an activity, creating a sub-activity, copying an activity, extending an activity, editing an activity, publishing or hiding a programme, viewing an activity's details, viewing activity names, managing the activity's schedule, editing the dates or schedule after registrations, closing (cancelling) an activity or group, and assigning a registration to a group and removing one from a group.
- Registrations: viewing registrations and managing a registration, approving a registration, rejecting one and resubmitting one, cancelling a registration, reactivating one and re-registering, transferring to another activity, marking as complete, requesting a cancellation, viewing the waiting list, viewing the school's waiting list, adding to the waiting list and moving a waiting-list entry to another activity, and exporting registrations to Excel.
- Payments: confirming a payment, marking a payment as made by the user, cancelling for non-payment, and refunding — the last being an ability granted by a separate decision, as in the final section of this page.
- Attendance and journals: taking session attendance, viewing attendance, marking with a note, writing a journal entry, viewing journal entries and publishing a journal entry.
- People: viewing administrators, creating or assigning an administrator, editing an administrator, deleting an administrator and verifying an administrator's email; viewing school managers, creating one, editing one and deleting one; and viewing trainers, creating a trainer, editing one and deleting one; and viewing trainer follow-up and exporting it (CSV).
- Students: viewing a student's health information, viewing a student's photo and media consent, viewing and managing a student's school record, viewing a student's past record, and correcting a student's name.
- Memberships and imports: viewing membership requests, managing membership and the join code and importing the school's student roster, and managing imports and committing the import of guardians, students, activities, registrations, payments and staff, and undoing an import.
- Reports, certificates and viewing: generating the attendance report and the activity report, sending the activity-start reminder email, sending the attendance-notes email and scheduling progress reports; viewing certificates and issuing a certificate and withdrawing a certificate — the last two being abilities granted by a separate decision, as in the final section of this page — and viewing the school dashboard and searching across the school, and viewing schools, viewing a school's details and editing a school.
It cannot: create a school or delete a school — those two being at platform level rather than branch level. Nor can it correct a guardian's email or manage partner integrations, both of which belong to the system administrator.
The usual job title: the school's owner, or the branch manager responsible for everything in it.
When to choose it over another: choose it only for someone who carries full responsibility for the branch — including its administrators, its trainers and its money. If what you need is "someone who runs the programmes and registrations" with no financial authority and no authority over people, the answer is ActivityAdmin.
ActivityAdmin
A wide operational role over programmes and registrations, but with no financial ability and no authority over people.
It can:
- Activities: viewing activities, viewing archived activities, creating an activity, creating a sub-activity, copying an activity, editing an activity, publishing or hiding a programme, viewing an activity's details, viewing activity names, managing the activity's schedule, assigning a registration to a group, and removing a registration from a group.
- Registrations: viewing registrations, managing a registration, approving a registration, rejecting one, resubmitting one, cancelling one, reactivating one, re-registering, transferring to another activity, marking as complete, requesting a cancellation, viewing the waiting list, viewing the school's waiting list, adding to the waiting list, moving a waiting-list entry to another activity, and exporting registrations to Excel.
- Attendance and journals: taking session attendance, viewing attendance, marking with a note, writing a journal entry, viewing journal entries, and publishing a journal entry.
- Students: viewing a student's health information, viewing a student's photo and media consent, and viewing a student's school record.
- Reports and viewing: generating the attendance report, generating the activity report, sending the activity-start reminder email, sending the attendance-notes email, viewing certificates, viewing the school dashboard, searching across the school, and viewing trainer follow-up (without exporting it).
It cannot: not a single financial operation — not confirming a payment, not marking a payment as made by the user, not cancelling for non-payment, and not refunding. Nor can it close (cancel) an activity or group, nor edit the dates or schedule after registrations, even though it creates and edits activities. Nor extend an activity (in force on the platform from 2026-08-28) — and with it the Renewals and Renewal collection tabs and the Resend renewal invitations button disappear from it, because one switch opens all four. And it holds no management of administrators or trainers, no import or membership ability, no issuing a certificate (it only views certificates), and neither viewing schools nor viewing a school's details.
The usual job title: the programmes manager or the activities officer at the branch.
When to choose it over another: choose it instead of SchoolAdmin when you want the programmes and registrations run completely without opening up the money or the management of people. And choose it instead of Coordinator when the person needs to publish or hide a programme or copy an activity — which a coordinator does not hold. As for extending and renewing, neither of them holds those any more: they sit with SchoolAdmin and ContentEditor.
Coordinator
A field role concerned with organising activities, groups, attendance and the student record, running the whole registration cycle with no financial operation at all.
It can:
- Activities: viewing activities, viewing archived activities, creating an activity, creating a sub-activity, editing an activity, viewing an activity's details, viewing activity names, managing the activity's schedule, editing the dates or schedule after registrations, closing (cancelling) an activity or group, assigning a registration to a group, and removing a registration from a group.
- Registrations: viewing registrations, managing a registration, approving a registration, rejecting one, resubmitting one, cancelling one, reactivating one, re-registering, requesting a cancellation, transferring to another activity, marking as complete, viewing the waiting list, viewing the school's waiting list, adding to the waiting list, moving a waiting-list entry to another activity, and exporting registrations to Excel.
- Attendance and journals: taking session attendance, viewing attendance, marking with a note, writing a journal entry, viewing journal entries, and publishing a journal entry.
- Students: viewing a student's health information, viewing a student's photo and media consent, viewing a student's school record, and managing a student's school record.
- Memberships: viewing membership requests, and managing membership and the join code.
- Reports and viewing: generating the attendance report, generating the activity report, sending the activity-start reminder email, sending the attendance-notes email, viewing certificates, viewing the school dashboard, searching across the school, viewing schools, and viewing a school's details.
Coordinator covers the request's cycle from beginning to end: approving a registration, rejecting one, managing a registration, resubmitting one, cancelling one and reactivating one, together with the whole waiting list.
What stays outside its hands is the money: not confirming a payment, not marking a payment as made by the user, not cancelling for non-payment, and not refunding. So if the request stops at a financial step, route it to Cashier, Finance or SchoolAdmin. See Rejecting a registration with a reason.
It cannot: any financial operation whatsoever — not confirming a payment, not marking a payment as made by the user, not cancelling for non-payment, and not refunding. Nor can it publish or hide a programme even though it creates activities, nor extend an activity, nor copy one, nor any import ability, nor the management of administrators and trainers, nor issuing a certificate or withdrawing one (it only views certificates).
The usual job title: an activities coordinator or a field supervisor over the groups.
When to choose it over another: choose it instead of ActivityAdmin when the work is organisational and in the field (groups, schedules, attendance and the student record) with full management of requests, and there is no need to publish or copy programmes. Note the reverse difference: a coordinator can close an activity and edit its dates after registrations, and an activity admin cannot. And extending an activity is held by neither — it sits with SchoolAdmin and ContentEditor.
Cashier
A payments desk with clear limits: it takes the amount, records it and follows the registration, and does not decide the request's fate.
It can:
- Payments: confirming a payment, marking a payment as made by the user, and cancelling for non-payment.
- Registrations: viewing registrations, managing a registration, viewing the waiting list, viewing the school's waiting list, and exporting registrations to Excel.
- Activities and viewing: viewing activities, viewing activity names, viewing an activity's details, viewing attendance, generating the attendance report, viewing the school dashboard, searching across the school, viewing schools, and viewing a school's details.
- Students: viewing a student's school record, and viewing a student's past record.
This role is a payments desk: confirming a payment, marking a payment as made by the user and cancelling for non-payment, together with managing a registration so it can open and follow the request, plus viewing the waiting list, viewing the school dashboard and searching across the school.
The decision on the request itself — approving a registration, rejecting one, reactivating one and transferring to another activity — is outside this role, and belongs with SchoolAdmin, ActivityAdmin or Coordinator. Nor does it hold refunding. See Access best practices.
It cannot: approve a registration, reject one, reactivate one or transfer to another activity — the decision on the request is not its business. Nor does it hold refunding. Nor can it mark attendance or take session attendance (it only views attendance), nor create, edit or publish an activity, nor write journals, nor view a student's health information, nor manage people, nor add to the waiting list (it only views it).
The usual job title: a receptionist or collector who takes cash amounts and records them.
When to choose it over another: choose it for whoever takes amounts, records them and follows the registration's status, without deciding its fate. And if their work is financial review and reading only, choose Finance. As for approving, rejecting and transferring, assign those to SchoolAdmin, ActivityAdmin or Coordinator. See Confirming a cash payment.
Finance
A narrow, precise financial role: it reads and confirms payments, and decides nothing about the request.
It can:
- Payments: confirming a payment.
- Registrations and reports: viewing registrations, exporting registrations to Excel, generating the activity report, and generating the attendance report.
- Viewing: viewing activities, viewing activity names, viewing an activity's details, viewing attendance, viewing the school dashboard, searching across the school, and viewing a school's details.
It cannot: approve a registration or reject one, nor refund, nor mark a payment as made by the user, nor cancel for non-payment. Nor can it take attendance, nor create or edit activities, nor see a student's health information.
The usual job title: the school's accountant or the collections and review officer.
When to choose it over another: both confirm payments and neither decides a registration, and the difference is in the kind of work rather than the decision: Cashier is a receiving desk, so it adds marking a payment as made by the user, cancelling for non-payment, managing a registration, viewing the waiting list and the student record; Finance is a reviewing position, so it adds generating the activity report, which Cashier does not hold. Choose Finance for whoever reviews and does not handle the receiving.
ContentEditor
A pure authoring and publishing role: it builds the programme catalogue and touches neither requests nor people.
It can:
- Activities: viewing activities, viewing archived activities, creating an activity, creating a sub-activity, copying an activity, extending an activity, editing an activity, publishing or hiding a programme, viewing an activity's details, and viewing activity names.
- Schedules: managing the activity's schedule.
It cannot: see registrations at all, nor attendance, nor the school dashboard, nor search across the school. Nor can it close (cancel) an activity or group, nor edit the dates or schedule after registrations, nor any financial operation.
The usual job title: the content or marketing officer who writes the programme descriptions and publishes them to families.
When to choose it over another: choose it instead of ActivityAdmin when the work is preparing and publishing the catalogue only; an activity admin adds to it the management of requests, attendance and journals. See Creating a new activity.
Integrations
A narrow data-exchange role: it reads activities and registrations and exports them.
It can:
- Viewing and exporting: viewing activities, viewing activity names, viewing an activity's details, viewing registrations, exporting registrations to Excel, and viewing a school's details.
It cannot: approve, reject or confirm a payment, nor take attendance, nor see the school dashboard, nor search across the school, nor manage people.
This role also carries old abilities named importing guardians from Excel, importing students from Excel, importing registrations from Excel and importing activities from Excel. Their screens were removed from the admin portal and replaced by the modern import path, which depends on other abilities that this role does not hold. So do not rely on it for importing; importing today happens from the import screens by whoever holds the modern import abilities — in practice SchoolAdmin.
The usual job title: a technical officer or a data partner who pulls periodic lists.
When to choose it over another: choose it instead of SupportReadOnly when the aim is exporting registration data; support sees but does not export. And if the aim is broad operational follow-up, choose support, because it sees the dashboard, search, the administrators and the trainers.
SupportReadOnly
A pure viewing role: zero writing abilities.
It can:
- Activities: viewing activities, viewing archived activities, viewing activity names, and viewing an activity's details.
- Registrations and attendance: viewing registrations, viewing the waiting list, viewing the school's waiting list, and viewing attendance.
- People: viewing administrators, viewing school managers, and viewing trainers.
- General viewing: viewing the school dashboard, searching across the school, viewing schools, and viewing a school's details.
It cannot: make any change however small. Nor does it see a student's health information, photo and media consent, or school record — it holds no ability in the students group at all. And it cannot export.
This role does not hold sensitive student data, but it does see students' names and their statuses in registrations, the waiting list, attendance and search. If the person is an outside contractor or an auditor, make your decision on that basis and do not describe the role as one that does not see students' data.
The usual job title: a support or assistance officer who follows cases and explains them without changing them.
When to choose it over another: choose it when the person needs to understand rather than to change; it is also the safe option for training or a temporary review. If they need to export the lists, choose Integrations.
SupportAgent
A platform-level role rather than a school-level one: it serves the request desk, and holds no ability on the schools' screens.
It can: see support tickets at every school, triage them, and answer them — those three being the whole of its abilities. And with them it reads the ticket's internal thread, which is where the support team discusses a school's data openly.
It cannot: anything else at all. It does not see activities, registrations, attendance or the school dashboard, and holds no writing ability outside the tickets.
The usual job title: a support agent on the platform's team, not a member of a school's staff.
When to choose it over another: never choose it for a member of a school's staff. Its reach goes beyond your school to other schools' families' tickets, which is why only a system administrator grants it. And if what you need is following up within your own school alone, the answer is SupportReadOnly.
The Choose role list is built according to who opens it, so this role is not shown to a school manager at all: a system administrator alone sees it, and alone assigns it. It used to be offered to everyone and then refused by the server after you pressed save; that is over. The server-side refusal is unchanged and deliberate: viewing all tickets is access that crosses schools.
ProviderManager
A seat for an employee of another company contracted by the school to deliver a particular programme (a gymnastics academy, for instance). It is the only role whose confinement to named activities is required: assigned school-wide, it grants nothing at all.
Can: inside their assigned activities only - view the activity and its details, place registrants into groups, view and export registrations, take attendance and write attendance notes, write journal entries and publish them to parents, send reminder and attendance-note messages, and issue and download completion certificates.
Cannot: anything at school level. No school dashboard, no student or parent directory, no health records, no school-wide search, no money operation of any kind (the school collects, the provider delivers), no approving or rejecting a registration - whether a child joins is the host school's decision - no managing the school's trainers, and no creating, editing or closing an activity.
Usual job title: a manager or coordinator at the contracted provider, not a member of school staff.
When to choose it over the others: when somebody from outside the school needs to run their programme on the platform. Do not use ActivityAdmin for this: every other supervisory role opens the student directory, the parent directory, school revenue and health records - which is precisely what an external party must not have.
For every other role, choosing specific activities is an optional narrowing. Here it is a condition: unless you pick particular activities, the holder sees nothing at all - deliberately, because an unbounded seat for an external company is worse than a seat that does not work. See Confine an administrator to specific activities.
Trainer
The role of whoever stands in front of the children in the session, confined to the activities assigned to them.
It can:
- Attendance: taking session attendance, viewing attendance, and marking with a note.
- Journals: writing a journal entry, viewing journal entries, and publishing a journal entry.
- Registrations: viewing registrations (the student roster for their own activities), exporting registrations to Excel, marking as complete, and sending the attendance-notes email.
- Students: viewing a student's health information, and viewing a student's photo and media consent — both deliberate, so the trainer knows the allergy, the medicine and the photography consent for the child in front of them.
- Activities: viewing an activity's details.
It cannot: see the school dashboard, search across the school, or see the lists of activities or schools. And it holds no approval, rejection or payment ability.
The usual job title: the activity's trainer or the programme's teacher.
When to choose it over another: this role is not assigned from the add-admin screen — a trainer is created from the trainers screen. And it is managed with Make dormant and Activate at each school, rather than by deleting. See Managing trainers and The trainer journal.
Parent
The families' app role, with nothing to do with the admin portal.
It can: use the parents app: registering their children and following their status. And it carries no administrative ability.
It cannot: anything inside the admin portal. And it is not available in the role list when adding an administrator.
The usual job title: the family themselves; the account is created when the guardian registers.
When to choose it over another: never choose it. If a guardian needs administrative access, add them with that same email under Add Admin and choose the appropriate administrative role for them; they will keep their guardian sign-in and gain an administrative sign-in on top of it. See Adding an administrator with particular permissions.
Abilities granted by a separate decision
Some abilities exist in the system but are not part of the recommended defaults for any role, and are granted one at a time and deliberately, because their effect is large or because they are at platform level rather than branch level:
| The ability | Why it is granted separately |
|---|---|
| Refunding | A reversing financial decision; it needs a clear owner inside the school |
| Issuing a certificate | A document that reaches the family in the school's name |
| Withdrawing a certificate | Going back on a document already issued |
| Correcting a guardian's email | It changes the family's door into their own account — the system administrator's business |
| Managing partner integrations | It opens data exchange with an outside party |
| Creating a school | At platform level rather than branch level |
| Deleting a school | At platform level rather than branch level, and its effect cannot be played down |
It is not enough for a person to hold the refund ability for the refund button to appear to them; there is also a system-level switch that has to be on first. So if the ability is granted and the button does not appear, the reason is usually that switch rather than the permission. See Troubleshooting access.
Frequently asked questions
What is the difference between Finance and Cashier?
Both can confirm a payment. Finance stops at reading, confirming and exporting reports. Cashier adds marking a payment as made by the user, cancelling for non-payment, managing a registration, viewing the waiting list, viewing a student's school record and viewing a student's past record. And neither of them decides the request's fate; approving, rejecting and transferring belong to other roles. See the capability matrix.
What is the difference between SchoolAdmin and ActivityAdmin?
SchoolAdmin holds nearly every ability at the branch, including the money and the management of administrators and trainers, imports and certificates. ActivityAdmin runs the programmes, registrations, attendance and journals with no financial ability and no authority over people, and cannot close an activity or edit its dates after registrations have begun. See Adding an administrator with particular permissions.
Can I make a new role that suits my school?
No. There are thirteen built-in roles only, and there is no button on the Roles & permissions screen for creating a new one; every row on it is tagged Built-in. The practical answer is to combine two roles on the same person, or for a system administrator to edit an existing role's abilities, bearing in mind that the change applies to everyone holding it at every school. See Roles and permissions.
Why does Trainer not appear in the role list when adding an administrator?
Because Trainer is deliberately excluded from the administrator assignment list, along with SystemAdmin and Parent, and the exclusion is enforced on the server rather than only in the interface. A trainer is created from the trainers screen, not from the administrators screen. See Managing trainers.
Can I give a person two roles at the same school?
Yes, and it is usually the safest way. Roles' abilities combine: whoever holds two roles has the union of their abilities, and no role cancels another. Use this to give a person a missing ability instead of editing the built-in role across the whole system. See Assigning administrators' roles per school.
What do I do if no role suits the case?
Start with the closest role and then add a second one covering the shortfall, which touches nobody but this person. Do not resort to editing a built-in role's abilities except by a system administrator's conscious decision, because the change alters the role's meaning for everyone holding it at every school. See The system administrator's playbook.
I gave a person a new role and they saw no difference — why?
Because abilities are loaded into a person's session when they sign in, so the change takes effect at their next sign-in or when the session refreshes. Ask them to sign out and back in. And if the button is still missing after that, the reason is usually that the role does not hold that ability at all. See The staff access lifecycle.