Skip to main content

The capability matrix: who holds each ability?

Goal​

This page is the mirror of the role catalogue: there you read the role and learn its abilities, and here you read the ability and learn who holds it. Use it when your question is of the kind "who can confirm a payment?" or "who sees a student's health information?" rather than "what does a coordinator do?".

Every mark in the tables below is taken from the permissions actually stored for the built-in roles today, not from the role's theoretical description. So you will find surprising results — and we have left them as they are, with a note where they sit.


How to read the matrix​

  • The first column is the ability's name as it appears on the Roles & permissions screen.
  • The remaining columns are the nine roles a school manager assigns, plus Trainer, in the order the columns appear: SchoolAdmin · ActivityAdmin · Coordinator · Cashier · Finance · ContentEditor · Integrations · SupportReadOnly (shortened to "Support" in the table headings) · Trainer · Provider manager (written "ProviderManager" in the table headings).
  • ✅ means the role actually holds this ability today. ❌ means it does not, so the button does not appear for it at all.
  • The brackets after a mark are a further limit, such as ✅ (for their assigned activities).
  • Abilities combine when more than one role is held at the same school; whoever holds two roles has the union of their abilities.
  • The scope is always one school: a ✅ means "within the school this role was assigned at" only.
Why is there no column for SupportAgent?

SupportAgent is a platform-level role rather than a school-level one: all three of its abilities are in support tickets, and it holds none of the abilities on this page. So its column would be ❌ on every single row. See its card in the role catalogue.

Why is there no column for SystemAdmin?

SystemAdmin is absent from the columns deliberately. It carries no stored abilities at all, but bypasses every permission check by design, and its row in the permissions editor is locked with the words Full access (locked). If we added it, its column would be ✅ on every line without exception, and it would ruin the table's readability. The detail is in The system administrator's playbook.

The ProviderManager column reads under one condition

Every ✅ in the Provider manager column is confined to the activities assigned to that seat, never to the school as a whole. "Mark session attendance" here means the children in their own programme, and no other activity in the school.

That confinement is a condition, not an option: assigned school-wide with no activities chosen, the seat grants nothing at all - unlike every other role. See its card in the Role catalogue.


Schools​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View schools✅❌✅✅❌❌❌✅❌❌
View a school's details✅❌✅✅✅❌✅✅❌❌
Edit a school✅❌❌❌❌❌❌❌❌❌
Import guardians from Excel — legacy✅❌❌❌❌❌✅❌❌❌
Import students from Excel — legacy✅❌❌❌❌❌✅❌❌❌
Import registrations from Excel — legacy✅❌❌❌❌❌✅❌❌❌
Import activities from Excel — legacy✅❌❌❌❌❌✅❌❌❌

Creating a school and deleting a school are held by no role — see the section on abilities no role holds by default, below.

The four abilities marked "legacy" do not work today

The old import screens using Excel files were replaced by the current import screens, which depend on entirely different abilities that SchoolAdmin holds and Integrations does not. So do not rely on these marks against Integrations when planning an import; the real abilities are in the imports table below.


Activities​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View activities✅✅✅✅✅✅✅✅❌✅
View activity names✅✅✅✅✅✅✅✅❌❌
View an activity's details✅✅✅✅✅✅✅✅✅✅
View archived activities✅✅✅❌❌✅❌✅❌❌
Create an activity✅✅✅❌❌✅❌❌❌❌
Create a sub-activity✅✅✅❌❌✅❌❌❌❌
Copy an activity✅✅❌❌❌✅❌❌❌❌
Extend an activity✅❌❌❌❌✅❌❌❌❌
Edit an activity✅✅✅❌❌✅❌❌❌❌
Publish or hide a programme✅✅❌❌❌✅❌❌❌❌
Edit the dates or schedule after registrations✅❌✅❌❌❌❌❌❌❌
Close (cancel) an activity or group✅❌✅❌❌❌❌❌❌❌
Assign a registration to a group✅✅✅❌❌❌❌❌❌✅
Remove a registration from a group✅✅✅❌❌❌❌❌❌✅
Rows worth noticing
  • ActivityAdmin — despite its name — does not hold closing (cancelling) an activity or group, nor editing the dates or schedule after registrations. Those two sit with SchoolAdmin and Coordinator only.
  • ActivityAdmin does not hold extending an activity since 2026-08-28. Extending is a commercial decision at school level, and it is the same switch that opens the Renewals and Renewal collection tabs and the Resend renewal invitations button for guardians — so withdrawing it hides those screens from it too. Grant it the ability by hand from the role editor if your school wants that.
  • Coordinator does not hold publishing or hiding a programme, nor copying an activity, nor extending one, so it builds the activity and does not publish it. See Creating a new activity.

Schedules​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
Manage the activity's schedule✅✅✅❌❌✅❌❌❌❌

Registrations​

This is the most important table on the page and the most used, and it is complete with nothing abbreviated.

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View registrations✅✅✅✅✅❌✅✅✅ (for their assigned activities)✅
Manage a registration✅✅✅✅❌❌❌❌❌❌
Approve a registration✅✅✅❌❌❌❌❌❌❌
Reject a registration✅✅✅❌❌❌❌❌❌❌
Resubmit a registration✅✅✅❌❌❌❌❌❌❌
Cancel a registration✅✅✅❌❌❌❌❌❌❌
Request a cancellation✅✅✅❌❌❌❌❌❌❌
Cancel for non-payment✅❌❌✅❌❌❌❌❌❌
Confirm a payment✅❌❌✅✅❌❌❌❌❌
Mark a payment as made by the user✅❌❌✅❌❌❌❌❌❌
Refund✅ (granted specially)❌❌❌❌❌❌❌❌❌
Reactivate a registration✅✅✅❌❌❌❌❌❌❌
Re-register✅✅✅❌❌❌❌❌❌❌
Mark as complete✅✅✅❌❌❌❌❌✅ (for their assigned activities)❌
Transfer to another school✅❌❌❌❌❌❌❌❌❌
Transfer to another activity✅✅✅❌❌❌❌❌❌❌
View the waiting list✅✅✅✅❌❌❌✅❌❌
View the school's waiting list✅✅✅✅❌❌❌✅❌❌
Add to the waiting list✅✅✅❌❌❌❌❌❌❌
Move a waiting-list entry to another activity✅✅✅❌❌❌❌❌❌❌
Export registrations to Excel✅✅✅✅✅❌✅❌✅ (for their assigned activities)✅
Generate the attendance report✅✅✅✅✅❌❌❌❌❌
Generate the activity report✅✅✅❌✅❌❌❌❌❌
Send the attendance-notes email✅✅✅❌❌❌❌❌✅ (for their assigned activities)✅
Send the activity-start reminder email✅✅✅❌❌❌❌❌❌✅
The two waiting-list abilities: one activity, or the whole school?

The waiting list has two viewing abilities, identical across the roles and different in scope:

  • View the waiting list opens the people waiting for one activity from the activity's header inside Registrations.
  • View the school's waiting list opens the Waiting list item in the sidebar, showing everyone waiting for a place at the school across every activity.

And they are granted today to the same roles, so you will not find a role that sees one without the other. Note too that viewing is not accepting: accepting from the list is governed by adding to the waiting list alone, which is why Cashier and SupportReadOnly see the whole queue without acting on it. See The waiting list.

Coordinator runs the whole registration desk with no financial ability

Coordinator holds the registration cycle from beginning to end: approving a registration, rejecting one, managing a registration, resubmitting one, cancelling one, reactivating one, re-registering and transferring to another activity, along with the whole waiting list.

Against that it holds no ability over 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 is held up on a payment, the financial decision sits with SchoolAdmin, Cashier or Finance. See Rejecting a registration with a reason.

Cashier is a payments desk and does not decide a registration's fate

Cashier holds the money side apart from refunding: confirming a payment, marking a payment as made by the user and cancelling for non-payment, with managing a registration, viewing registrations, viewing the waiting list, viewing the school's waiting list, exporting registrations to Excel, viewing the school dashboard and searching across the school. And it does not hold refunding.

But it does not decide the registration itself: not approving one, not rejecting one, not reactivating one, and not transferring to another activity. So route those decisions to SchoolAdmin, ActivityAdmin or Coordinator — and that is the separation between whoever collects the money and whoever decides the registration. See Best practices in managing access.

Finance is a "read and confirm" role only

Finance holds confirming a payment and nothing else among the financial abilities: no approving or rejecting a registration, no refunding, no marking a payment as made by the user, and no cancelling for non-payment. See Confirming a cash payment.


Attendance​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View attendance✅✅✅✅✅❌❌✅✅✅
Take session attendance✅✅✅❌❌❌❌❌✅✅
Mark with a note✅✅✅❌❌❌❌❌✅✅

See Taking session attendance.


Journals​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
Write a journal entry✅✅✅❌❌❌❌❌✅✅
View journal entries✅✅✅❌❌❌❌❌✅✅
Publish a journal entry✅✅✅❌❌❌❌❌✅✅

The journals are confined to five roles: SchoolAdmin, ActivityAdmin, Coordinator, Trainer and Provider manager - the roles that stand in front of the children, plus the two that supervise them. See The trainer journal.


Weekly plans​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View weekly plans✅✅✅❌❌❌❌❌✅❌
Write a group's weekly plan✅✅✅❌❌❌❌❌✅❌
Send a weekly plan to parents, and withdraw it✅✅✅❌❌❌❌❌✅❌

Weekly plans are confined to four roles: SchoolAdmin, ActivityAdmin, Coordinator and Trainer. Provider manager is deliberately not among them - a contracted provider runs its own sessions but does not write the school's weekly plan. And as with the journals, writing one and sending it to parents are two different abilities: holding the first does not publish anything.


Students​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View a student's health information✅✅✅❌❌❌❌❌✅❌
View a student's photo and media consent✅✅✅❌❌❌❌❌✅❌
View a student's school record✅✅✅✅❌❌❌❌❌❌
Manage a student's school record✅❌✅❌❌❌❌❌❌❌
View a student's past record✅❌❌✅❌❌❌❌❌❌
Correct a student's name✅❌❌❌❌❌❌❌❌❌
Children's data — grant it with care

Viewing a student's health information and viewing a student's photo and media consent sit with Trainer deliberately, so the adult standing in front of the child knows what concerns the allergy, the medicine and the photography consent. And it is personal data about children, so grant it only to those who actually supervise children, and review the list regularly.

SupportReadOnly holds none of the abilities in this group: not health information, not photo and media consent, and not a student's school or past record.

But it is not a role without children's data

The absence of this group from SupportReadOnly does not mean it does not see students. It holds viewing registrations, viewing the waiting list, viewing the school's waiting list, viewing attendance and searching across the school — and those screens show students' names and their statuses, and the school's waiting list shows them across every activity on one screen. What it lacks is the sensitive data alone. Take that into account before assigning the role to an outside contractor or an auditor, and do not describe it to anyone as one that does not see students' data.

See Best practices in managing access.


Memberships​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View membership requests✅❌✅❌❌❌❌❌❌❌
Manage membership and the join code✅❌✅❌❌❌❌❌❌❌
Import the school's student roster✅❌❌❌❌❌❌❌❌❌

Reviewing membership requests and managing the join code sit with SchoolAdmin and Coordinator. Importing the school's student roster sits with SchoolAdmin alone. See Managing guardians and students.


Imports​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
Manage imports✅❌❌❌❌❌❌❌❌❌
Commit the guardians import✅❌❌❌❌❌❌❌❌❌
Commit the students import✅❌❌❌❌❌❌❌❌❌
Commit the activities import✅❌❌❌❌❌❌❌❌❌
Commit the registrations import✅❌❌❌❌❌❌❌❌❌
Commit the payments import✅❌❌❌❌❌❌❌❌❌
Commit the staff import✅❌❌❌❌❌❌❌❌❌
Undo an import✅❌❌❌❌❌❌❌❌❌

The whole of the current import path is in SchoolAdmin's hands alone. And the Integrations role — contrary to what its name suggests — is a narrow data-exchange role: it reads activities and registrations and exports them, and holds none of the current import abilities.


Trainers​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View trainers✅❌❌❌❌❌❌✅❌❌
Create a trainer✅❌❌❌❌❌❌❌❌❌
Edit a trainer✅❌❌❌❌❌❌❌❌❌
Delete a trainer✅❌❌❌❌❌❌❌❌❌
View trainer follow-up✅✅❌❌❌❌❌❌❌❌
Export trainer follow-up (CSV)✅❌❌❌❌❌❌❌❌❌
Re-read a closed trainer follow-up week✅❌❌❌❌❌❌❌❌❌

See Managing trainers.


School managers​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View school managers✅❌❌❌❌❌❌✅❌❌
Create a school manager✅❌❌❌❌❌❌❌❌❌
Edit a school manager✅❌❌❌❌❌❌❌❌❌
Delete a school manager✅❌❌❌❌❌❌❌❌❌

See Managing school managers.


Administrators​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View administrators✅❌❌❌❌❌❌✅❌❌
Create or assign an administrator✅❌❌❌❌❌❌❌❌❌
Edit an administrator✅❌❌❌❌❌❌❌❌❌
Delete an administrator✅❌❌❌❌❌❌❌❌❌
Verify an administrator's email✅❌❌❌❌❌❌❌❌❌

SupportReadOnly sees the lists of administrators, school managers and trainers and can change nothing in them — and that is the role's definition: pure reading with no writing at all. See Adding an administrator with particular permissions.


Certificates​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View certificates✅ (granted specially)✅ (granted specially)✅ (granted specially)❌❌❌❌❌❌✅
Issue a certificate✅ (granted specially)❌❌❌❌❌❌❌❌✅
Withdraw a certificate✅ (granted specially)❌❌❌❌❌❌❌❌❌

Competitions​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View a competition console✅✅✅❌❌❌❌✅❌❌
Organise a competition✅✅❌❌❌❌❌❌❌❌
Report match results✅✅✅❌❌❌❌❌❌❌

"Organise a competition" is the organiser's ability: settings, participants, fixtures and approving results. "Report match results" is the referee's - they report a result, they do not approve it. That is why a Coordinator holds the second and not the first.


Dashboards​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
View the school dashboard✅✅✅✅✅❌❌✅❌❌

ContentEditor, Integrations, Trainer and Provider manager do not see the school dashboard at all. See Understanding the dashboard indicators.


The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
Search across the school✅✅✅✅✅❌❌✅❌❌
Who does not hold the search?

Four roles do not hold searching across the school: ContentEditor, Integrations, Trainer and Provider manager. And whoever does not hold this ability does not see the search screen at all, because what you do not hold does not appear to you. See The command palette.


Progress reports​

The abilitySchoolAdminActivityAdminCoordinatorCashierFinanceContentEditorIntegrationsSupportTrainerProviderManager
Manage the progress-report schedule✅ (granted specifically)❌❌❌❌❌❌❌❌❌

Scheduling progress reports is a school-level decision, so it is confined to the SchoolAdmin alone.


Abilities no role holds by default​

The following abilities exist in the system, but are granted within no recommended set. That is deliberate: they are granted one at a time and on purpose, or they stay outside the school's scope entirely.

The abilityIts position today
Create a schoolHeld by no role — a platform-level decision.
Delete a schoolHeld by no role — a platform-level decision.
Correct a guardian's emailHeld by no role — the system administrator's business.
Manage partner integrationsHeld by no role, not even Integrations.
RefundNot part of the recommended set. SchoolAdmin holds it today because it was granted on purpose, and there is a system-level switch that has to be turned on before the refund button appears at all.
Issue a certificate and withdraw a certificateNot part of the recommended set. SchoolAdmin holds them today by a deliberate grant.
Reset to recommended defaults removes everything granted specially

What is marked on this page as "granted specially" — along with viewing certificates for SchoolAdmin, ActivityAdmin and Coordinator, and scheduling progress reports for SchoolAdmin — is not part of the recommended set for those roles. And the Reset to recommended defaults button replaces the set entirely; and because no role today is missing anything from its recommended set, this button's effect is removal only, and it adds no ability to any role. The button saves nothing by itself: it shows a preview, Apply to the form only stages the change on screen, and nothing is saved until you press Save changes — and once saved, it cannot be undone from the screen. Its effect on each role is set out in The system administrator's playbook — review it before saving, because some roles lose abilities your team relies on today: Coordinator loses building, editing, closing and scheduling activities, and Cashier loses seven reading abilities it uses daily.

Treat this button as a last resort on a role nobody uses, not a tidying tool for a role in service. See Troubleshooting access.


Notes about what appears on screen​

Differences between the table and the screen
  • Four group headings still appear in English inside the Arabic screen: Memberships, Imports, Partners and Certificates. Your colleagues using the portal in Arabic see this; you will not.
  • The four entries importing guardians from Excel, importing students from Excel, importing registrations from Excel and importing activities from Excel are old remnants: their screens were replaced, and importing today happens from the current import screens with the abilities set out in the imports table above.
  • The send the activity evaluation ability is retired: its button no longer appears in Registration management, and the permissions editor no longer offers it. SchoolAdmin, ActivityAdmin and Coordinator still hold it, so it shows among their permissions as "Send activity evaluation (retired)" - and it allows nothing.
  • The schedule progress reports ability really is held by SchoolAdmin, but it does not appear in the permissions editor, so do not look for it there.
  • What you do not hold does not appear to you: buttons and screens are hidden rather than merely disabled.

Frequently asked questions​

Who can confirm a payment?​

Three roles only: SchoolAdmin, Cashier and Finance. No other role holds confirming a payment, including ActivityAdmin and Coordinator. Marking a payment as made by the user and cancelling for non-payment sit with SchoolAdmin and Cashier only, and refunding with SchoolAdmin alone. See Confirming a cash payment.

Who can reject a registration?​

SchoolAdmin, ActivityAdmin and Coordinator — the same three roles that hold approving a registration. Neither Cashier nor Finance nor the remaining roles hold rejecting a registration. See Rejecting a registration with a reason.

Who sees a student's health information?​

SchoolAdmin, ActivityAdmin, Coordinator and Trainer. It is not seen by Cashier, Finance, SupportReadOnly, ContentEditor or Integrations. And it is personal data about children, so keep the list of who holds it short and review it regularly. See Best practices in managing access.

Why can I not find an ability on the screen?​

For three reasons: either your role at this school does not hold it, so the screen or button is hidden entirely; or the ability was added to you just now and your session has not refreshed yet, so you need to sign out and back in; or the ability itself does not appear in the permissions editor, as with scheduling progress reports. See Troubleshooting access.

How do I find out a particular member of staff's permissions?​

Open their roles at that school — a school administrator from Edit Admin on the person's row, a system administrator from Schools & roles, which is the only screen showing every branch at once — then combine those roles' rows on this page: the member of staff's abilities are the union of all their roles' abilities at the same school, and abilities never cancel one another. See Assigning administrators' roles per school.

What can a cashier decide and what can they not?​

They decide the money side apart from refunding: confirming a payment, marking a payment as made by the user and cancelling for non-payment. And they open and manage the registration, see registrations, the waiting list, attendance and the school dashboard, export registrations and search across the school. They do not decide the registration's own fate: no approving, no rejecting, no reactivating and no transferring to another activity, and they do not hold refunding. See the role catalogue.

What is the difference between this page and the role catalogue?​

This page is ordered by ability, so it answers "who holds this ability?", and the role catalogue is ordered by role, so it answers "what can this role do?". The source is the same and the ordering differs. See the role catalogue.