Skip to main content

When to grant a role and when to edit its permissions — a decision guide

Goal​

This page is the practical decision guide for anyone managing access on the platform. It answers one question that comes up every week: do I assign this person a role, or edit the role itself? You will find here who decides what, a four-question decision tree, the safety steps before any change, fifteen real cases with their steps, and the warnings that must not be crossed.


The golden rule​

The golden rule

Grant a role — do not edit a role.

Assigning a role concerns one person at one branch, and its effect is confined to them. Editing a role's permissions, by contrast, changes the meaning of the role itself for everyone holding it, at every school — because the role is shared across the whole platform, and there is no private copy of it for your school.

So: assigning is the ordinary daily action, and editing is the rare, last one.


Who decides what​

The decisionSchoolAdminSystemAdmin
Adding a member of staff and assigning their roles at their branch✅✅
Changing a member of staff's roles within their branch from Edit Admin✅✅
Deleting an administrator from the school✅✅
Managing a person's roles across several branches from the Schools & roles screen❌✅
Editing the role's own permissions❌✅
Resetting a member of staff's password❌✅
Searching for an administrator across every school❌✅

The dividing line is not "who touches roles" but where. SchoolAdmin is the senior administrator at their branch: they add staff, choose their roles, change them later from Edit Admin, and delete them — all within their branch. What goes beyond a single branch — the Schools & roles screen, which manages a person's roles at several branches, and searching for an administrator across every school — belongs to SystemAdmin alone, and cannot be granted to another role because it is not offered in the permissions editor at all. And the meaning of a role itself is edited only by SystemAdmin, because its effect reaches across every branch.

If the Schools & roles button does not appear

That is expected if you are not a system administrator. Change the member of staff's roles at your branch from Edit Admin, and do not treat the button's absence as a fault. And if the member of staff works at more than one branch, the matter needs a system administrator.


The decision tree in four questions​

  1. Is the problem with one person, or with the role itself?
    • One person needs an ability they do not hold: do not open the permissions editor at all. Assign them an additional role at their branch — the decision is made.
    • Everyone holding this role needs the same ability: go to question 2.
  2. Is the need temporary or permanent?
    • Temporary (covering leave, a registration season, a limited task): assign an additional role now, and set yourself a reminder to withdraw it later — the decision is made.
    • Permanent: go to question 3.
  3. Is there a ready-made role that holds the ability needed?
    • Yes: assign that role alongside their current one. Permissions combine when more than one role is held, and none cancels another — the decision is made.
    • No ready-made role suits: go to question 4.
  4. And only then: is it right for this role to change for everyone holding it at every school?
    • No: stop. Redistribute the job to another role, or use a second role for the person concerned.
    • Yes: edit the role — after carrying out the four safety steps in the next section.
The situationThe right action
One person is short of somethingAssign them an additional role at their branch
A temporary needA temporary role, withdrawn when the task ends
A person moved to another branchAssign them to the new branch, then unassign from the old
The assignment has endedUnassign from the branch, or disable the account
A permanent need shared by everyone holding the roleEdit the role's permissions after the safety steps

Before any change to a role — four safety steps​

  1. Record the current state before you change it. Open Roles & permissions then Edit permissions, and write down the abilities enabled for this role today. There is no way to restore a previous set with one press, so your written record is the plan for going back.
  2. Add, do not remove. Adding opens a door that was not open; removing may stop people working at other schools you do not know and whose screens you cannot see.
  3. Change one ability at a time, then save. Large changes all at once make diagnosing any fault impossible. Press Save changes after each change, and check the effect before the next one.
  4. Tell those affected that the change takes effect at their next sign-in. The save message says so itself: that the changes take effect at the affected administrators' next sign-in (or when their session refreshes). So anyone staying inside their open session carries on with their old permissions for a short while.

Fifteen cases and what to do about them​

Which screen you use depends on which role you hold

Schools & roles is SystemAdmin-only. No role holds the permission behind that button, so a school administrator does not see it. Wherever a case below says Schools & roles, a school administrator does the single-branch equivalent instead:

To do this at your own branchA school administrator usesA system administrator uses
Add or withdraw a roleEdit Admin on the person's rowSchools & roles, on that branch's card
Take the person out of the branchDelete on the person's rowUnassign from school, on that branch's card
See every branch a person works at— (ask a system administrator)Schools & roles

And Delete at a school is not the whole account: it removes that school's link, and disables the administrative account entirely only when it was the person's last branch — the same rule as unassigning.

1. A new member of staff joining the school​

The situation: a new member of staff has started and needs access to the admin portal. The decision: grant a role. This case has nothing to do with the permissions editor at all. The steps: People > Admins > Add Admin > fill in the name and email and choose at least one role > Save, then copy the one-time password and hand it to them directly, because it does not appear again. Why: the built-in roles are ready and designed for this purpose; using them as they are is quicker and safer than manufacturing an exception. The detail is in Adding an administrator with particular permissions.

2. A member of staff covering a colleague on leave​

The situation: the registrations officer is on leave for a fortnight, and their colleague needs to cover the work. The decision: assign the colleague a temporary additional role, and touch neither the role nor the traveller's account. The steps: a school administrator opens Edit Admin on the colleague's row, adds the traveller's role to the roles already there, and saves; a system administrator can do the same from Schools & roles on that branch's card with Add a role… and Save roles. On their return, remove that role again the same way. Why: holding more than one role is safe because permissions combine, and undoing the assignment takes one press. The full screen steps are in Assigning administrators' roles per school.

3. Moving a member of staff from one branch to another​

The situation: a member of staff has moved from the Riyadh branch to the Jeddah branch. The decision: assign them to the new branch first, then unassign them from the old one. The steps: from the new branch use Assign existing, search for the member of staff by name, mobile number or email, select them, set their roles at this branch, then Assign to this school. Once the new branch's card appears in Admin schools & roles, open the old branch's card and press Unassign from school. Why: unassigning from the last branch disables the administrative account entirely rather than just the branch, so the order here is not a formality.

4. A member of staff working at two branches at once​

The situation: one accountant serves two branches, and may need a different role at each. The decision: one account, an assignment at each branch with its own roles. Do not create them a second account. The steps: from the second branch use Assign existing, search by name, mobile number or email, select them, set their roles for this branch, then Assign to this school. Why: the role decides what the person does and the branch decides where they do it; so they can be SchoolAdmin at one branch and Finance at another on the same account.

5. A member of staff leaving​

The situation: a member of staff has left and their access must stop today. The decision: unassign them from every branch, or disable their administrative account by deleting it — now, not after telling them. The steps: at your own branch, press Delete on the administrator's row — that removes this school's link, and disables the whole administrative account only if it was their last branch. Where the person works at several branches, a system administrator does it from Schools & roles with Unassign from school on each branch card. To stop their administrative access everywhere, every branch has to be dealt with; the last one to go is what disables the account and ends the session, and the record is kept either way. And adding the same email again later revives that same account and ends its open sessions, then an Admin re-added card says what happened to its password: usually the old one stops working and a new one-time password is emailed to the person, so do not reset their password afterwards; the old one is kept only when this sign-in is used for more than admin access at that school — see Returning or reappointment before bringing back any account that was stopped for a reason. Why: stopping concerns the administrative persona alone; so if the person is also a guardian, their sign-in to the parents app stays as it is. And after it is done they cannot sign in again, but their open session may work for a few minutes. Signing out ends that immediately, but it is their decision — so ask for it in a friendly departure and do not rely on it otherwise. The detail on an unfriendly removal is in The staff access lifecycle.

6. A guardian who works at the school and needs an administrative account​

The situation: a guardian already registered on the platform has been employed by the school and needs administrative access. The decision: do not create them a new email or a second account — give their existing account an additional administrative persona. The steps: Add Admin with that same email, choose the roles, and save > the system stops and shows that this email already has an account > review the roles and press Grant admin access to confirm. The first attempt, before confirming, changes nothing at all. Why: the person keeps their current guardian sign-in (mobile number and verification code) and gains an administrative one-time password on top of it: one person, one email, two personas.

7. A trainer who also does coordination work​

The situation: a trainer also handles coordinating activities and needs the administrative screens. The decision: create them a separate administrator persona on the same email. Do not try to promote the trainer account from the role list. The steps: Add Admin with the same email, choose the appropriate administrative role such as Coordinator or ActivityAdmin, and confirm through Grant admin access if the system asks. The trainer's data, attendance and journals stay as they are. Why: the Trainer role is not available at all in the Add Admin role list — trainers are created from the Trainers screen through Add Trainer, and the exclusion is enforced at server level rather than only in the interface. See Managing trainers.

8. An outside contractor for a limited period​

The situation: an outside designer or operator needs access for one season. The decision: grant the narrowest role that covers their work, and set yourself a reminder to withdraw the access when the period ends. The steps: add them with one role only, matching their job — ContentEditor for whoever writes and publishes activities, or SupportReadOnly for whoever only needs to look — then when the contract ends press Unassign from school. Why: ContentEditor sees no registrations, no attendance and no school dashboard at all; its work is confined to creating, editing and publishing activities and managing their schedule. That confinement is the protection itself.

9. An auditor or reviewer who only needs to look​

The situation: an internal auditor or a consultant wants to understand the position without changing anything. The decision: SupportReadOnly alone, and nothing else. The steps: add them with the SupportReadOnly role at the required branch only, and review the list when the review has finished. Why: this role is pure reading with no write operation at all: it sees activities, archived activities and an activity's details, the registration lists and the waiting list, attendance, the school dashboard, and the lists of administrators, school managers and trainers, and it uses search across the school. And it holds no permission over sensitive student data — not health information, not photo and media consent, and not a student's record.

Take care before assigning it to an outside reviewer

"Read only" means without writing, not without children's data: the registrations, waiting list, attendance and search screens show students' names and their statuses. If the reviewer is from outside the school, make the decision on that basis, restrict it to the branch required, and unassign as soon as the review ends.

10. A member of staff short of just one button​

The situation: a member of staff works well in their role, but needs one action they do not hold. The decision: add a second role. The answer here is "add a role" in nearly every case, and not "edit the role". The steps: Edit Admin on the person's row > add the smallest role that holds the missing ability alongside the roles already there > save. (A system administrator can do the same from Schools & roles.) And before saving, read the rest of the abilities of the role you are about to add, so you do not grant more than you mean to. Why: the best-known example is Coordinator: it runs registrations completely — approving, rejecting and the waiting list — but holds no payment ability, so neither confirming a payment, nor marking a payment as made by the user, nor cancelling for non-payment, and it cannot publish or hide a programme. So rather than editing the role for every coordinator on the platform, add the person a role that genuinely holds the missing ability, or route these cases to a member of staff who already holds it. Compare the roles in the capability matrix.

11. A member of staff who cannot see their branch's data​

The situation: a member of staff says they hold the right role but cannot see their branch's data. The decision: check the scope first, not the role. The steps: open Admin schools & roles and make sure there is a card for that specific branch and that their roles on it are saved. If the card is not there, assign them to the branch. And if it is there and correct, ask them to sign out and back in. Why: holding the role at one branch grants nothing at another, and the check happens on the server with every request. And buttons and whole screens are hidden from anyone without the ability for them, so "the button is not there" usually means "the role does not hold this ability here" or "they have not signed in again yet". See Troubleshooting access.

12. A member of staff asking for full access​

The situation: a member of staff asks for the SchoolAdmin role to be rid of repeated permission requests. The decision: refuse by default. Full access is not the answer to a missing permission. The steps: ask them which specific action was blocked, then handle it as case 10 — a narrower additional role. And keep the SchoolAdmin role for the trusted school owner alone. Why: SchoolAdmin is full authority over the branch, and the system warns you itself when you choose it. Granting it to make daily work easier effectively abolishes every separation of duties at the school.

13. A permanent need shared by everyone in the role​

The situation: everyone holding the role, at your school and at others, permanently needs the same ability. The decision: this is the one rare case where the role is edited — and it is taken only by a system administrator. The steps: carry out the four safety steps, then: the sidebar > Platform > Roles & permissions > Edit permissions on the role in question > enable one ability > Save changes. And tell those affected that the effect starts at their next sign-in. Why: there is no school selector on the screen, because the role is global by nature; which is why the built-in roles carry an explicit warning that this is a built-in role used across the whole system and its permissions should be edited with care. And there is no button for creating a new role, so editing is the only tool — a further reason for using it rarely. Note too that some group headings still appear in English inside the Arabic screen today (certificates, imports, memberships, partners).

14. Separation of duties on the money path​

The situation: you want the person who approves a registration not to be the one who confirms its payment, nor the one who refunds it. The decision: the platform already separates the payments desk from the registration decision; your job is to keep them with two different people. The steps: assign Cashier or Finance to whoever receives the money; assign the registration decision — approving and rejecting — to Coordinator, ActivityAdmin or SchoolAdmin; make sure the two sides do not meet in one person; and keep refunding in the narrowest scope possible, with SchoolAdmin alone. Why: the roles themselves are built around that separation:

  • Finance is a genuinely narrow financial role: it confirms payments, reads, and generates reports, and neither approves nor rejects a registration, does not mark a payment as made by the user, does not cancel for non-payment, and does not refund.
  • Cashier is the payments desk — it confirms a payment, marks a payment as made by the user and cancels for non-payment; it manages a registration, views registrations and exports them to Excel; and it reads the waiting list, attendance, a student's school and past record, and the school dashboard, and searches across the school. It neither approves nor rejects a registration, and does not hold refunding.
  • Refunding is not part of the recommended defaults for any role, and is granted today to SchoolAdmin by a deliberate decision. And above that there is a system-level switch that must be on before the refund button appears at all.

See Confirming a cash payment and Access best practices.

15. Urgent access outside working hours​

The situation: an emergency in which you need to open or close access immediately. The decision: assign or unassign now, and never open the permissions editor under pressure. The steps: to open: add the role from Edit Admin (or Schools & roles if you are a system administrator), then ask the person to sign out and back in so they take the permissions immediately — and here co-operation is assured, because they are the beneficiary. To close: Delete at your branch immediately, or Unassign from school if you are a system administrator; a new sign-in is prevented at once, and the open session carries on working for up to about 15 minutes with no way on the screens to end it sooner. Why: permissions are loaded into a person's session at sign-in, so nothing in this system takes effect instantaneously. When opening, you can speed the effect up by signing out and back in; but in an urgent closure, do not build your plan on the other party's co-operation — act immediately, and tell a system administrator if the person's abilities touch sensitive data or financial actions. As for editing a built-in role under time pressure, that is the quickest way to cause a wide fault at other schools.


Warnings not to be crossed​

Reset to recommended defaults replaces the whole set once saved, and cannot be undone

The Reset to recommended defaults button saves nothing by itself: it opens a preview titled Recommended defaults for "{role}" that lists These capabilities will be removed first and then These capabilities will be added, and says plainly: "Nothing is saved until you press Save changes." Apply to the form then only stages the change on screen, and Cancel closes the preview with nothing changed. Nothing is saved until you press Save changes.

But what you save after Apply to the form replaces the current set entirely with the recommended set. And no role today is missing anything from its recommended set, so the button's effect is removal only: it adds no ability to any role. This is exactly what it will remove:

The roleWhat it removes
SchoolAdminViewing certificates, issuing a certificate, withdrawing a certificate, refunding, and scheduling progress reports
ActivityAdminViewing certificates
CoordinatorViewing certificates and all of its activity-authoring abilities: creating an activity, creating a sub-activity, editing an activity, closing (cancelling) an activity or group, editing the dates or schedule after registrations, managing the activity's schedule, viewing schools and viewing a school's details
CashierViewing 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
Finance, ContentEditor, Integrations and SupportReadOnlyNothing — exactly matching the recommended set
TrainerNot applicable — there is no recommended set for this role, and the button refuses to work on it

And the button gives nothing back for what it takes: it strips Coordinator of activity authoring entirely, and takes seven reading abilities away from Cashier that it relies on in its daily work — without granting either of them any new ability. The danger is that it is complete, and cannot be undone from the screen once saved.

Do not apply and save it on a role in use merely to tidy up. And if you want a particular outcome from the table above, carry it out by hand, ability by ability with Save changes, so you stay in control of every step.

Read the confirmation before you take someone out of a branch

Unassign from school asks you to confirm, and the wording changes with the situation. Where the person works at other branches it says they will be removed from this school only and their other schools are unaffected. Where this is their last branch it says so plainly: it disables their whole admin account and ends their session, and they can be restored later by re-adding the same email.

Delete at a school, by contrast, shows one warning in its confirmation that applies if this is the person's last school, without saying whether that is their case. So if you delete from the Admins list, confirm how many branches they have in Schools & roles first. And when moving between branches, assign the new branch first.

SchoolAdmin is full authority over the branch

When the SchoolAdmin role is chosen, — full access appears beside it with an orange warning saying the role grants full authority over this school and should be given only to a trusted school owner.

Do not assign it to make daily work easier or to avoid asking for a missing permission. And for information, SystemAdmin alone is the one shown marked Full access (locked), whose permissions cannot be edited at all, since it bypasses every permission check.


The expected outcome​

  • Most daily access requests are handled by assigning or withdrawing a role, without opening the permissions editor at all.
  • Each role's meaning stays stable at every school, so comparing and auditing roles remains possible.
  • Every rare change to a role is recorded beforehand, confined to a single ability, and communicated to those affected.
  • You know in advance that any change's effect starts at the person's next sign-in, so you do not read the delay as a fault.
  • The money path stays distributed between more than one person, and refunding stays in the narrowest scope.

Frequently asked questions​

When do I edit the role instead of assigning a second one?​

Only when the need is permanent and shared by everyone holding the role at every school, and no ready-made role covers it. Otherwise, assigning is always the right answer. See the comparison of roles in the capability matrix.

I added a role for the member of staff and they saw no difference — why?​

Because permissions are loaded into a person's session when they sign in, so their open session keeps its old permissions. Ask them to sign out and back in for the effect to show immediately. The detail is in Assigning administrators' roles per school.

I want to give a member of staff just one action — can I?​

A single action cannot be granted to a single person; the assignable unit is the role. Add them a second role that holds that action, after reviewing the rest of its abilities, because permissions combine and do not conflict. Look at the roles in the role catalogue.

Nothing is saved yet: a preview shows what would be removed and what would be added, and Apply to the form only stages the change on screen. If you then press Save changes, the role's abilities are replaced with the recommended set entirely. And no role today is missing anything from its recommended set, so the effect is removal only with no addition — such as removing viewing certificates, refunding and scheduling progress reports from SchoolAdmin. The full table of what happens to each role is in the warnings section above. Do not save it on a role in service, and if it has been saved, see Troubleshooting access.

Can a trainer become a coordinator on the same email?​

Yes, but not by changing their role. Create them an administrator persona on the same email through Add Admin and choose Coordinator, because the Trainer role is not available in the administrators' role list and is created from the trainers screen. See Managing trainers.

Who approves the registration and who receives the payment?​

The registration decision — approving and rejecting — sits with Coordinator, ActivityAdmin and SchoolAdmin. Receiving the money sits with Cashier, which confirms a payment, marks a payment as made by the user and cancels for non-payment without approving or rejecting a registration, and with Finance, which confirms payments only. Keep the two sides with two different people, and start from Access best practices.

The member of staff cannot see their branch's data — is the problem the role?​

Usually not. Start with the scope: make sure the person appears in your branch's Admins list with their roles saved, because a role at one branch does not work at another. A system administrator can see every branch at once under Schools & roles. The full diagnostic steps are in Troubleshooting access.

Can I make a role of my own?​

No. The roles are built in and their number is fixed at thirteen, and there is no button for creating a new one; the administrators' role list offers ten of them to a system administrator and nine to a school manager, who can assign all nine. Handle any special need by combining more than one role on the same person. The detail of each role is in the role catalogue.