Best practices for managing your school team's permissions
Goal
The principles here are not a local invention; they are the same principles used in international information-security practice, such as those underlying ISO/IEC 27001 and the frameworks published by NIST. But a principle alone protects no school; what protects one is translating it into a specific step on a specific screen. So the rest of this page sets out each principle in three parts: what it is, how you carry it out inside Skool.Cool exactly, and the sign that tells you you are breaking it today.
Eight principles and how they work in practice
1. Least privilege
The principle: grant a person the narrowest role that covers their work, then add more when a real need appears — and never grant in advance "just in case".
How you apply it here:
- For anyone who only needs to look (following up, support, verbal reports) assign SupportReadOnly: it sees activities, registrations, the waiting list and the school dashboard, and can write nothing at all.
- For anyone who only prepares activities assign ContentEditor: creating an activity, editing it, publishing or hiding a programme and managing the activity's schedule — with no registrations, no attendance, no dashboard and no searching across the school.
- Do not assign SchoolAdmin except to someone who genuinely owns the school or runs it entirely. The Add Admin screen warns you itself that the role grants full authority over this school and should be given only to a trusted school owner.
- If a person is short of one ability, add them a second role from Add a role… rather than promoting them to full access.
The sign you are breaking it: more than half your team holds SchoolAdmin.
2. Separation of duties
The principle: one person should not control the money's path from beginning to end; whoever approves a registration does not confirm its payment, and whoever confirms a payment does not refund it.
How you apply it here:
- Divide the path between three people: approving a registration with one, confirming the payment with another, and refunding with a third.
- Today only SchoolAdmin holds the refund ability, so complete separation for refunds means either confining it to one person holding SchoolAdmin, or asking a system administrator to add the ability to a narrower role — bearing in mind that the change applies to everyone holding that role at every school.
- The Finance role suits the payment side alone perfectly: it holds confirming a payment and holds neither approving a registration, nor rejecting one, nor refunding, nor cancelling for non-payment, nor marking a payment as made by the user.
- Refunding is not part of the recommended defaults for any role; it is granted individually and deliberately, and SchoolAdmin holds it today because it was granted to it on purpose. And there is a system-level switch that must be on before the refund button appears at all.
The system separates the payments desk from the registration decision: Cashier is a pure payments desk — it holds confirming a payment, marking a payment as made by the user, cancelling for non-payment, managing a registration, viewing registrations and exporting registrations to Excel, and holds neither approving a registration, nor rejecting one, nor refunding. And the registration decision sits with ActivityAdmin, Coordinator or SchoolAdmin. But that separation collapses the moment both roles meet in one person: abilities combine and do not cancel, so whoever holds the payment role and the approval role together has both abilities in their hands, and no screen shows that as a warning. Real separation is the school's responsibility in how it distributes people, not the roles' responsibility alone.
Coordinator holds approving a registration, rejecting one, managing a registration, resubmitting a registration, cancelling a registration, reactivating a registration and the full set of waiting-list abilities. Against that it holds no payment ability whatsoever: not confirming a payment, not marking a payment as made by the user, not cancelling for non-payment, and not refunding. That makes it the natural counterpart to the payments desk — the registration decision with them, the money with somebody else — provided it is not the same person.
The sign you are breaking it: the person who approved the registration is the same one who confirmed its payment.
3. An account for each person, and no shared accounts
The principle: each person has one account under their own email. A shared account destroys any ability to know who did what, and cannot be withdrawn from one person without disabling the rest.
How you apply it here:
- In Add Admin the email address is required and is the sign-in name; make it the person's own email, not a department's or an office's.
- If the person is already an administrator at another branch, no second account is created for them: a system administrator assigns them through Assign existing and then Assign to this school, because its search works for nobody else. If you are a school administrator, ask the support team for the assignment through Help or request.
- If the person is a guardian at your school, enter that same email in Add Admin. The system stops you with This email already has an account and asks for explicit confirmation through Grant admin access. The first, unconfirmed attempt changes nothing. After confirming, their guardian sign-in stays as it is and an administrative one-time password is added: one person, one email, two identities.
- The one-time password is shown once only; hand it to its owner directly and do not post it in a group chat. And nobody — not even a system administrator — can read an existing password.
The sign you are breaking it: an email named "reception" or "the office" that three people take turns on.
4. The role before the exception
The principle: meet a shortfall by assigning a ready-made role or a second role to the person, not by editing the role's own definition.
How you apply it here:
- There are thirteen built-in roles, and there is no button for creating a new one on the Roles & permissions screen.
- Editing a role's permissions from Edit permissions changes that role's meaning for everyone holding it at every school, because the role is general at system level. Assigning a role to a person from Admin schools & roles, by contrast, affects that person at that school alone.
- Roles' permissions combine: whoever holds two roles gets the union of their abilities, and no role cancels another. This is the safe way to give someone an extra ability without touching the role.
- The screen warns you itself when you open a built-in role: that it is a built-in role used across the whole system, and to edit its permissions with care.
The Reset to recommended defaults button 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 current permission set with the recommended set entirely, in one go. And the effect today is pure removal with no addition: roles granted abilities outside the recommended defaults lose them, and roles that already match their defaults are unchanged. It removes the certificate abilities, refunding and scheduling progress reports from SchoolAdmin; it strips Coordinator of activity authoring and scheduling and of viewing certificates, viewing schools and viewing a school's details; and it takes seven viewing abilities away from Cashier that it actually works with: viewing attendance, viewing a student's past record, generating the attendance report, viewing the waiting list, viewing the school's waiting list, viewing schools and viewing a school's details. Against that, Finance, ContentEditor, Integrations and SupportReadOnly lose nothing at all because their permissions match the recommended defaults exactly, and Trainer has no recommended defaults in the first place so the button refuses to work on it. Treat this button as a last resort on a role nobody uses, not as a tidying tool on a role in service — and the full table of its effect on each role is in the system administrator's playbook.
The certificates, memberships, imports and partners groups have no Arabic heading yet, so their headings appear in English inside the Arabic screen. The ability names inside them are in Arabic as usual. You will not see this yourself while the portal is in English.
The sign you are breaking it: you opened Edit permissions because one member of staff needed one ability.
5. Reviewing permissions regularly
The principle: permissions accumulate and never retreat of their own accord; whatever is not reviewed regularly swells quietly.
How you apply it here:
- Fix a date each term for the review, and make it one named person's job rather than "management's" in general.
- Review from two screens only: People > Admins to find who holds what and where, and Roles & permissions to find what each role means.
- Work the ready-made list at the end of this page (seven items): who holds SchoolAdmin, who is still assigned to a branch they left, who holds two roles they no longer need, who can view a student's health information, who holds the payment abilities, who has not signed in for a long time, and which role has had its permissions edited since the previous review.
- Record the review's outcome and who carried it out; a review that leaves no trace turns into a review that does not happen.
The sign you are breaking it: you cannot say when the last review was or who did it.
6. Joining, moving and leaving
The principle: access follows the change in the job on the same day — the day they start, the day they move, and the day the work ends.
How you apply it here:
- Joining: add the person with their roles from their first day through Add Admin, or — if they are an administrator at another branch — through Assign existing, which works for a system administrator alone. Saving an administrator requires at least one role to be chosen, so settle the role from the start rather than "we will sort it out later".
- Moving between branches: add the new branch and its roles first, then unassign from the old branch on the same day — because unassigning from the last branch disables the administrative account entirely. Adding alone leaves the person seeing the data of a branch they no longer work at. The removal is done from Admin schools & roles with the Unassign from school button.
- Leaving: the Delete button on an administrator stops the access and keeps the record, and a system administrator can later revive the same account by adding the same email again, rather than creating a new one. A school administrator most likely cannot do this themselves, and asks the support team for it through Help or request. A Trainer, by contrast, is managed with Make dormant and Activate for each school separately, which is a reversible action that keeps the record.
- Timing: withdrawing access prevents a new sign-in immediately, but an open session keeps its old abilities until it refreshes — in practice up to about fifteen minutes. Signing out ends that at once, but depends on the person's co-operation, so do not count it as a guarantee in an unfriendly removal; carry out the withdrawal immediately and count the window into your plan.
Taking someone out of a branch — Delete at your own school, or Unassign from school for a system administrator — asks you to confirm. If that branch was this person's last, they are not merely taken out of it: their whole administrative account is disabled and their session ends. The Unassign from school confirmation names which case you are in, while the Delete confirmation shows this warning without saying whether it is theirs — so ask a system administrator how many branches the person works at before you delete.
The sign you are breaking it: a member of staff who moved a month ago is still showing on both branches' cards.
7. Protecting system administrator accounts
The principle: an account that bypasses every permission check needs higher protection — and needs to number more than one.
How you apply it here:
- Keep more than one SystemAdmin account so the school cannot lock itself out if one becomes unreachable.
- Do not use it for daily work. Whoever runs activities and registrations day to day works with a narrower role, and keeps the system administrator account for its own tasks.
- Treat it as the account that changes the meaning of every role: its row in the permissions editor is locked and shows Full access (locked), with a message saying it has full access and bypasses every permission check, so its permissions cannot be edited.
- SystemAdmin is not offered in the Add Admin role list at all, and the exclusion is enforced on the server rather than only in the interface — so it cannot be worked around.
- The Reset password button on an administrator's row appears for a system administrator alone; make the request for a reset travel through a known channel rather than a passing message.
The sign you are breaking it: only one system administrator account, and it is used for daily tasks.
8. A clear and reviewable trail
The principle: every change to roles and permissions has a written reason, a known owner, and a date to look at it again.
How you apply it here:
- When granting an ability outside the recommended defaults — refunding, issuing a certificate or withdrawing a certificate, say — write in the school's record who asked for it, why, and when it is to be reviewed.
- Keep that record somewhere management can reach, not in a private conversation.
- The screen reminds you that the change is not immediate: it says the changes take effect at the affected administrators' next sign-in (or when their session refreshes). So do not assume the job is done the moment you save.
- At the termly review make the rule explicit: any sensitive ability with no owner and no written reason is the first thing to go.
The sign you are breaking it: you are looking at a sensitive ability and nobody at the school knows who asked for it or why.
Children's data privacy
Viewing a student's health information and viewing a student's photo and media consent are not ordinary administrative fields; they are personal data belonging to children, and are subject to the Kingdom's personal data protection rules. The two abilities exist for a clear operational reason: so that the adult standing in front of the child knows about an allergy, a medicine or a photography consent before they need to, not afterwards.
How to handle them:
- Grant them on a need-to-know basis only: to whoever actually supervises the children. Today they are held by SchoolAdmin, ActivityAdmin, Coordinator and Trainer.
- Trainer holds them deliberately, so that they can see the safety cards for the child in front of them, even though it has no dashboard, no searching across the school, and no approval or payment ability at all.
- SupportReadOnly holds none of the sensitive student-group abilities — not health information, not photo and media consent, and not a student's record. But it is not a role without children's data: it holds viewing registrations, viewing the waiting list, viewing attendance and searching across the school, and those screens show students' names and their statuses. Treat it on that basis when assigning it to an outside contractor, and never describe it to anyone as a role that "does not see students' data".
- Review the list of who holds these two abilities at the end of every term, rather than once at set-up.
Do not copy health information or photo consent states into spreadsheets, do not send them in group chats, and do not save them on a personal device. Data inside the system is governed by permissions and by the school's scope; outside it, nothing governs it and it cannot be recalled once it has spread.
A checklist for the termly review
Work this list once each term, and record its outcome and who carried it out:
- Who holds SchoolAdmin? Open People > Admins and review everyone holding this role. Any name that does not own the school or run it entirely moves to a narrower role.
- Who is still assigned to a branch they have left? Open Admin schools & roles for every administrator working at more than one branch, and remove the branches they no longer work at with Unassign from school — noting that removing the last branch disables the account entirely.
- Who holds two roles they no longer need? On each school's card, delete the unnecessary role's chip and press Save roles. Remember that saving requires at least one role.
- Who can view a student's health information and photo and media consent? The list should be confined to those actually supervising children this term.
- Who holds the payment abilities? Review who holds confirming a payment, marking a payment as made by the user, cancelling for non-payment and refunding, and make sure approval, payment and refunding are not all with one person.
- Who has not signed in for a long time? A dormant account is an open permission serving no purpose; disable it or remove its assignment.
- Which role has had its permissions edited since the previous review? Open Roles & permissions and compare each role against what is written in your school's record, and remove every ability with no written reason.
Frequently asked questions
How many people should hold SchoolAdmin?
As few as possible — usually the school's owner and their deputy only, because the role grants full authority over the branch. And for anyone needing one extra ability, assign a second role rather than a full promotion. The detail of each role is in the role catalogue.
Can a cashier approve or reject a registration?
No. The role is a payments desk: it holds confirming a payment, marking a payment as made by the user, cancelling for non-payment, managing a registration, viewing registrations and exporting registrations to Excel, and holds neither approving a registration, nor rejecting one, nor refunding. The registration decision sits with ActivityAdmin, Coordinator or SchoolAdmin. And it remains for you to make sure no one person holds both the payment role and the approval role, because the two roles' abilities combine for them. Compare the roles in the capability matrix.
I want to give one member of staff one extra ability — do I edit the role?
No. Editing the role changes its meaning for everyone holding it at every school. The right way is to assign that member of staff a second role at their school from Add a role…, so the two roles' abilities combine for them alone. The step-by-step is in Assigning administrators' roles per school.
Can I use Reset to recommended defaults to tidy the roles up?
It is not advisable on a role in service: the button saves nothing by itself and only shows a preview, but saving what you applied from it with Save changes replaces the current set entirely. And the effect is pure removal with no addition: every ability granted outside the recommended defaults is removed, and anything already matching its defaults is unaffected — the certificate abilities, refunding and scheduling progress reports for SchoolAdmin, activity authoring and scheduling for Coordinator, and seven viewing abilities for Cashier. Use it only on a role nobody uses, and read the full table of its effect in the system administrator's playbook.
A member of staff moved to another branch — what exactly do I do?
Add the new branch with its roles, then unassign them from the old one — both steps on the same day, because adding alone leaves them seeing the data of a branch they have left. And note that removing the last branch disables the account entirely — the Unassign from school confirmation says which of the two is about to happen, so read it. The full sequence is in The staff access lifecycle.
Why does a trainer see a student's health information?
Because they are the adult standing in front of the child, and need to know about an allergy, a medicine and the state of photography consent before the session rather than after it. And their role stays narrow all the same: no dashboard, no searching across the school, and no approval or payment ability. See Managing trainers.
I changed the permissions and the member of staff saw no difference — why?
Because abilities are loaded into a person's session when they sign in, so they stay on their old abilities until the session refreshes — in practice up to about fifteen minutes, or immediately if they sign out and back in. If the problem persists after that, see Troubleshooting access.