Skip to main content

Roles and permissions — who can do what?

Goal​

This page is the starting point for understanding access in Skool.Cool: what the account types are, the difference between a role, a permission and a scope, and what each role can actually do today. Read it first, then move on to the Roles and access chapter for the full detail.


The four account types​

TypeWhat this account isWhere it works
ParentThe end-user account: registers their children and follows their registrations. It grants no ability inside the admin portal.The parents app
TrainerA narrowly scoped operational account tied to the activities assigned to them. Created from the Trainers screen, not from the add-admin screen.The admin portal (limited scope)
Admin, with their rolesA member of school staff. Their abilities are not fixed: they are the sum of the roles assigned to them at that branch.The admin portal
SystemAdminFull platform-level access, bypassing every permission check. Cannot be assigned from the Add Admin screen.The admin portal

One account can hold more than one capacity at the same time: a parent and an admin together. Granting the admin capacity does not remove their access as a parent, and withdrawing it does not disable their account in the parents app.


Three concepts: role, permission and scope​

  • A permission — one precise ability, such as approving a registration, confirming a payment, or taking session attendance.
  • A role — a named bundle of permissions. There are thirteen built-in roles only, and there is no way to create a new one from the interface. A role means the same thing at every school.
  • A scope — the school (branch) at which a person holds that role. The role decides what; the scope decides where.

Example: Sarah holds Finance at the Riyadh branch and SupportReadOnly at the Jeddah branch. In Riyadh she can confirm payments; in Jeddah she cannot write anything at all — the same person, a different role because it is a different branch. Sarah cannot see the data of a branch she was never assigned to, and that check happens on the server with every request.

Editing a role affects everyone

Assigning a role to a person changes that person alone, at that branch. Editing the role's own permissions changes what the role means for everyone who holds it, at every school. If you want to give one person an extra ability, add another role to them instead of editing the role.


Two rules you have to know​

Abilities add up; they never conflict

Someone holding more than one role at the same school gets the abilities of all of them. Permissions are combined and never cancel each other out, so no role "restricts" another. This is the safe way to give a person one extra ability without touching a role.

A change takes effect at the next sign-in

Permissions are loaded into a person's session when they sign in. Any change — a new role, a withdrawn role, an edited permission — does not appear in the session currently open, but at the next sign-in or when the session refreshes. The screen itself says so: saved changes take effect the next time the affected admins sign in (or when their session refreshes). Withdrawing access blocks a new sign-in immediately, but an open session may keep working for a few minutes afterwards — details on urgent termination in The staff access lifecycle.


The thirteen roles at a glance​

RoleIn one lineWhat sets it apart
SystemAdminFull platform-level access.Holds no stored permissions at all, because it bypasses every check; its row is locked and it cannot be assigned from the add-admin screen.
SchoolAdminFull access within the branch.The only role that manages admins, trainers and imports, and the only one that imports the school's student roster. It cannot create or delete a school, correct a guardian's email, or manage partner integrations.
ActivityAdminRunning activities and registrations across the whole school.Creates, publishes and extends activities, and approves and rejects registrations, and sees the school dashboard — but with no financial ability whatsoever, and cannot close an activity.
CoordinatorDay-to-day running of activities, schedules, attendance and the registration desk.Approves, rejects and manages registrations and runs the waiting list; closes an activity and edits dates after registrations exist; searches across the school; and handles viewing membership requests and managing membership and the join code. No financial ability, and cannot publish a program.
CashierThe payments desk and following payment status.Confirms payments, marks a payment as made by the user, cancels for non-payment, and manages registrations; sees the school dashboard and searches across the school. Does not approve or reject registrations, and cannot issue refunds.
FinanceFinancial read access and confirming payments.Confirms payments, generates reports and exports registrations, but does not approve, reject, refund, or cancel for non-payment.
ContentEditorAuthoring and publishing activities only.No registrations, no attendance, no dashboard, no search.
IntegrationsA narrow data-exchange role: viewing and exporting activities and registrations.Its Excel import abilities are legacy and their screens have been removed; importing today happens from the import screens with a role that holds the import abilities — in practice, SchoolAdmin.
SupportReadOnlyPure read access with no writing at all.Sees the lists, the school dashboard and search. Does not see a student's health information or school record — but does see student names in registrations and attendance.
SupportAgentAnswering and triaging support tickets.A platform-level role rather than a school-level one: it sees support tickets at every school, and triages and answers them. Which is why only a system administrator may grant it — a school administrator granting it would be handing out access to other schools' families' threads. Distinct from SupportReadOnly, which is confined to its own school and writes nothing.
ProviderManagerA manager at a contracted company, running their own programme.Confined to the activities assigned to it and nothing else: sees the activity and its registrations, places registrants into groups, takes attendance, writes journal entries and issues certificates. No dashboard, no search, no financial ability, and cannot approve or reject a registration. Assigned with no activities chosen, it grants nothing at all.
TrainerFollows the activities assigned to them.Sees and exports the registration roster for their activities and marks a registration complete; takes session attendance and writes journal entries; sees a student's health information and media consent. No dashboard, no search, and no payment or approval abilities.
ParentA parents-app account.Holds no stored permissions, grants nothing inside the admin portal, and cannot be assigned from the add-admin screen.

The Add Admin list shows what its opener can actually assign, not a fixed list. A system administrator sees ten roles: the thirteen less SystemAdmin, Parent and Trainer, which cannot be assigned from this screen at all — an exclusion enforced on the server, not only in the interface. A school administrator 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 is granted only by a system administrator, because its reach crosses school boundaries.

The list changes according to who opens it

The list used to show SupportAgent to everyone and let the server refuse it on saving. It no longer does: it is now built from the roles its opener can actually assign, so a school manager is never shown a role that would be refused after they filled in the form. The server-side refusal is unchanged — the list now agrees with it instead of contradicting it.

A full card for every role — with all its permissions and limits — is in the role catalogue.


A short matrix​

This is a compact matrix of the most-asked-about abilities, reflecting what the roles hold in the system today.

AbilitySchoolAdminActivityAdminCoordinatorCashierFinanceTrainer
View activities✅✅✅✅✅❌ (sees details of their assigned activities only)
Create an activity✅✅✅❌❌❌
Publish/hide a program✅✅❌❌❌❌
Approve a registration✅✅✅❌❌❌
Reject a registration✅✅✅❌❌❌
Confirm a payment✅❌❌✅✅❌
Take session attendance✅✅✅❌❌✅ (their activities only)
Generate an attendance report✅✅✅✅✅❌
View the school dashboard✅✅✅✅✅❌
View trainer follow-up✅✅ (for their assigned activities, if their assignment is limited)❌❌❌❌
Export trainer follow-up (CSV)✅❌❌❌❌❌
Re-read a closed trainer follow-up week✅❌❌❌❌❌
Coordinator and Cashier — mirror images

Coordinator runs the registration desk and never touches money. They approve, reject and manage registrations and run the waiting list, but they cannot confirm a payment, mark a payment as made by the user, or cancel for non-payment.

Cashier is the exact opposite. They own the payments desk entirely, and decide nothing about a registration: they neither approve nor reject it. If one person needs both sides, assign them both roles — and be aware that this removes the separation of duties.

The full matrix of every role against every ability is in the capability matrix.


Where it lives​

Sidebar > the Platform group > Roles & permissions.

The screen is available to SystemAdmin. It lists every role, each tagged Built-in, and there is no button to create a new one. Pressing Edit permissions opens the capability matrix grouped by domain, and then Save changes. There is no school selector on this screen, because a role is system-wide; assignment per branch happens on a different screen.

The SystemAdmin row appears as Full access (locked) with the edit button disabled, alongside this notice: SystemAdmin has full access and bypasses every permission check — its permissions cannot be edited.

Opening any other role shows a second notice: this is a built-in role used across the whole system; edit its permissions carefully.

Reset to recommended defaults removes, and does not add

Reset to recommended defaults saves nothing by itself: it previews what would be removed and what would be added, Apply to the form only stages the change on screen, and nothing is saved until you press Save changes. But what you then save replaces the permission set entirely: it removes every permission outside the recommended set, today it adds nothing to any role, and once saved it cannot be undone from the screen. So read the These capabilities will be removed list before you save, and treat it as a last resort on a role nobody is using. A table of its effect on every role is in the SystemAdmin playbook.


Where to go next​


Frequently asked questions​

Where do I find the roles and permissions screen?​

From the sidebar, open the Platform group and then Roles & permissions. The screen is available to SystemAdmin, and it is where a role's own abilities are set. Assigning roles to a particular member of staff happens on a different page — see Assigning admin roles per school.

Why did the staff member not see the new permission after I edited it?​

Because permissions are loaded into their session when they sign in. After Save changes, the edit takes effect at their next sign-in or when their session refreshes, not in the session already open. Ask them to sign out and back in. See Troubleshooting access.

How do I give someone a role at just one branch?​

Roles are assigned per school. Open the card for the branch you want on the staff member's roles page, add the role, then press Save roles. The full steps are in Assigning admin roles per school.

What is the difference between Finance and Cashier?​

The opposite of what the names suggest: Finance is the narrower role. It confirms payments and views registrations, attendance and the school dashboard, generates the attendance and activity reports, and exports registrations — and it does not approve or reject a registration, refund an amount, or cancel for non-payment. Cashier is wider on the financial side: it confirms payments, marks a payment as made by the user, and cancels for non-payment, and manages registrations, views the waiting list and the school dashboard, and searches across the school — and it too neither approves nor rejects registrations, and cannot refund. Compare the two in detail in the role catalogue.

Why can I not edit SystemAdmin's permissions?​

Because it has no stored permissions to begin with: it bypasses every permission check, so its row shows as locked with the edit button disabled. To grant an extra ability, edit the appropriate role such as SchoolAdmin or Coordinator instead, or give the person a second role. See the SystemAdmin playbook.