Skip to main content

The button is missing? Troubleshooting permissions

Goal​

To diagnose access and permission problems in the admin portal and fix them yourself: symptom → most likely cause → fix. This page covers the situations schools actually meet, from "the button is not showing" to "I changed the permissions and nothing happened", and sets out when the fix is in your hands and when the matter has to go to a system administrator.


Start here — four diagnostic questions​

Do not edit any role before you have answered these four questions in order. Start with the first: it is the cheapest and the quickest, and many cases end there.

1. Have they signed out and back in since the last change?​

A person's abilities are loaded into their session at the moment they sign in. Any change after that — adding a role, withdrawing a role, editing a role's abilities — does not show for them until their session refreshes, which is within about a quarter of an hour at most, or immediately if they sign out and back in.

Where to check: ask them to sign out and back in in front of you, then try again. The save message itself points this out: it says the changes take effect at the affected administrators' next sign-in, or when their session refreshes.

2. Are they assigned to the right school?​

The role says what the person can do, and the scope says where. Anyone assigned to only one branch does not see another branch's data, even if they hold the same role name elsewhere — and the check happens on the server for every request, not in the browser.

Where to check: the sidebar > People > Admins, inside the branch in question — if the person is not in that list, they are not assigned to it. To see every branch at once, a system administrator presses Schools & roles on the person's row, which opens Admin schools & roles with a card for each school; no other role can open that page.

3. Do they hold the right role at that school?​

On the branch's card, the Roles in this school section shows the roles assigned to them there specifically. A person may hold more than one role at the same school, and the abilities of all of them are combined — abilities accumulate and do not cancel one another.

Where to check: the chips shown under Roles in this school on that branch's card.

4. Does that role hold the ability at all?​

This is the step that is usually forgotten. Some roles do not hold abilities you would expect them to — a live example: Coordinator holds no payment ability whatsoever, so Confirm payment will not appear for them however many times they sign out and back in.

Where to check: the sidebar > Platform > Roles & permissions > Edit permissions beside the role. Or see the capability matrix and the role catalogue.

Editing a role changes its meaning at every school

Roles are defined at whole-system level. Adding an ability to a role grants it to everyone holding that role at every school. If what you need is an exception for one person, the narrower answer is to add them a second role at that school, not to edit the role itself.


The symptom table​

The symptomThe most likely causeThe fix
The button is not showing at allThe role does not hold the ability at this branch; buttons are hidden rather than shown disabled. Or they have not signed out and back in since the last change.Work through the four questions above, then either add them a role that holds the ability at that school, or add the ability to the role from Edit permissions.
A no-permission message when opening a pageThe page was opened by a direct link or from a bookmark, and the check is repeated on the server, which refuses the request.The page itself now names the missing permission — copy it and send it to whoever can edit roles; it is the same name shown in Edit permissions. Do not try to work around the message.
"Your changes were not saved" or "The group was not created" when saving an existing activity or adding a group to itThe page opened, but the save itself was refused: the activity (or the activity the group belongs to) is outside the schools assigned to you, or outside the activities assigned to you if your scope is limited to specific ones. A group whose main activity is in your scope is covered by it, and its save is not refused even if the group was created after your scope was saved.Nothing was saved, and what you entered is still in the form. Ask the school admin to add the activity to your scope from the Admins screen, then save again from the same page.
"The activity was not created" when creating a new activityYour role cannot create activities in this school, or the school is not one of the schools assigned to you. The activity was never created, so it cannot be added to anyone's scope.Nothing was created, and what you entered is still in the form. Ask the school admin to give you a role in this school that can create activities, or to create the activity themselves and then add it to your scope.
"You don't have permission to do this for this activity" when saving a coach noteThe note is about a student outside the group assigned to you, or about a program you are not assigned to.The note you wrote is still in the text box and was not sent. Ask the school to assign you to the student's group, then save it again.
I changed the permissions and nothing happenedThe change really was saved, but the person's session still carries their old abilities.Ask them to sign out and back in. Do not repeat the change believing it was not saved.
The member of staff sees only one branchThey are assigned to one branch; and the scope is checked on the server for every request.From the Admins screen inside the other branch, a system administrator presses Assign existing, searches for them, and chooses their roles at that branch; its search works for nobody else. If you are a school administrator, ask the support team for it through Help or request.
The member of staff sees no data after being addedThey have not signed in since the assignment, or their role holds no viewing abilities in the first place (like ContentEditor, which holds neither viewing registrations, nor viewing the school dashboard, nor searching across the school).Sign in again first. If the screens stay empty, the role is not right for the job — see the capability matrix.
Save roles is disabledYou removed every role chip from the school's card, so the message appeared asking you to choose at least one role or unassign the administrator from this school.Put at least one role back, or use Unassign from school to take them out of the branch entirely.
Save is disabled in add-adminA required field is missing (first name and email address) or no role was chosen.Complete the required fields and choose at least one role from Choose role.
The email is already registeredThe email belongs to an account already in the system.If its owner is already an administrator, a system administrator assigns them through Assign existing, and a school administrator asks the support team for that through Help or request. If it is a non-administrative account (a guardian, say), confirm through Grant admin access; the first, unconfirmed attempt changes nothing.
A former member of staff can still get in for a few minutesTheir open session keeps its abilities until it refreshes, even though the access was removed and they cannot sign in again.There is no way on the screens to end an open session immediately. Signing out ends it but is in the person's hands — ask for it in a friendly departure only. Otherwise: carry out the removal immediately and tell a system administrator if their abilities were sensitive. See The staff access lifecycle.
The coordinator cannot see Confirm paymentThe Coordinator role holds no payment ability at all. That is its actual state, and not a fault.Route confirming payments to Cashier or Finance, or add the coordinator a second role that holds the ability at that school. The detail is in the longer explanation below.
A permission group's heading shows in English on the Arabic screenFour groups' headings are not translated yet: Imports, Memberships, Certificates and Partners. Your colleagues using the portal in Arabic will see this; you will not.There is nothing to fix; only the heading is untranslated, the ability names inside it are in Arabic, and it works like every other group.
Trainer does not appear in the role listThe Trainer role cannot be assigned from Add Admin, and the exclusion is enforced on the server so it cannot be worked around.Create the trainer from the Trainers screen — see Managing trainers.
The Reset password button does not appearThat button is for a system administrator alone.Ask a system administrator to do it; a one-time password is created, handed to the member of staff, and they are asked to change it at first sign-in.
Reset to recommended defaults removed permissions that were workingWhat was applied from the button's preview and then saved with Save changes replaces the role's whole set of abilities rather than adding to it. The button alone saves nothing.Grant the missing abilities again one by one from the same screen. The detail and the full list are in the longer explanation below.
Taking someone out of their last branch disables the whole account

Do not use either Delete or Unassign from school to experiment. Both ask you to confirm, and the confirmation names which is about to happen: removal from this school alone, or — if this was the last branch they are assigned to — their whole administrative account disabled and their session ended.


The longer explanations​

Why the button disappears instead of appearing disabled​

The admin portal is built from the session's own abilities: whatever the account holder does not have the ability for is not drawn on the screen at all — not the button, and sometimes not the whole page. So "the button is missing" is not a fault; it is the way the system says "this role does not hold this ability at this school".

And hiding the button is not the protection. The same check is repeated on the server with every request, so anyone opening the page by a direct link has their operation refused and sees the no-permission message rather than having it carried out.

Which means there are only two reasons for a missing button: either the role does not hold the ability, or the person holds it but has not signed in since the last change. Always start with the second, because it is cheaper.

One exception worth knowing

The refund ability has an extra system-level switch that must be on before the refund button appears. So a role may hold the ability and the button still not appear — and that case goes to a system administrator.

What to read on the Access forbidden page, and what to do with it​

The refusal page no longer stops at "You don't have permission to view this page". It now names the missing permission in a box below the message, with a line asking you to copy the name and send it to whoever can grant it.

Why it matters: before this change a member of staff passed a general sentence on to the administrator, who then started guessing from scratch — which role? which ability? The written name cuts all of that short, and it is the same name shown beside the ability in Roles & permissions > Edit permissions, so you can search for it there directly.

Two cases to read carefully:

  • One name: that is the permission required; there is no alternative to it.
  • "This page requires ANY ONE of the following permissions:" followed by several names: any one of them is enough to open the page. There is no need to grant them all; choose the one that best fits the member of staff's job.
Sometimes no name appears, and that is correct

If you reach the page with no permission name, the refusal was not about a missing ability but about the kind of account — someone who is not a trainer opening a screen meant for trainers, for example. There is no name to ask for here; the fix is the right account or role, not adding an ability.

An important note: a permission's name appearing does not mean that granting it is right. Read what that ability opens in the capability matrix before granting it, especially if it concerns payments or children's data.


Why a change does not take effect immediately, and what to do​

At sign-in a person's abilities are loaded into their session and stay with them as they are. Any change after that — a new role, a withdrawn role, an ability added to or removed from the role — is saved in the system straight away, but reaches their open session only when it refreshes: within about a quarter of an hour at most, or immediately if they sign out and back in.

Both screens say so themselves: that the changes take effect at the affected administrators' next sign-in (or when their session refreshes), and that the roles were updated and the changes take effect at the administrator's next sign-in.

What to do:

  1. Do not make the change again — it is already saved, and repeating it confuses you without speeding anything up.
  2. Ask the person to sign out and back in, and check with them in front of you.
  3. When withdrawing access urgently, remove the access immediately and do not put it off. Signing out ends their session at once but depends on their co-operation, so do not treat it as a guarantee in an unfriendly removal — count the few intervening minutes into your plan.

Why a role's limits surprise you, and how to check instead of guessing​

Roles are not a ladder from narrowest to widest; each one is built around a particular job, so a role that looks small may hold an ability that a wider-looking one does not. Which is why intuition is no use for answering "should this person be able to do that?".

Live examples:

  • Coordinator runs the whole registration desk: approving a registration, rejecting one, managing a registration and the waiting-list abilities — and yet holds no payment ability at all, and cannot publish or hide a programme.
  • Cashier is the payments desk: confirming a payment, marking a payment as made by the user, and cancelling for non-payment. It opens a registration and works with it through managing a registration, viewing registrations and viewing the waiting list, but does not decide it: it neither approves nor rejects, and holds no refund ability.
  • Finance confirms payments only, and holds neither marking a payment as made by the user, nor cancelling for non-payment, nor refunding, nor deciding registrations.
  • ActivityAdmin decides registrations and publishes programmes, and holds no payment ability at all.

How to check: open the capability matrix and read the ability you want against the role's column, or open Edit permissions beside the role itself on the Roles & permissions screen. That is the only reliable answer; anything else is a guess.

If it turns out the role does not hold the ability, you have three answers, ordered from narrowest to widest:

  1. Add the person a second role at the same school (the recommended answer), because roles' abilities combine and do not cancel one another. Open Edit Admin on their row and add the role alongside the ones already there. (A system administrator can instead use Add a role… on that branch's card under Admin schools & roles.)
  2. Route the job to another member of staff who holds a role with the ability. That is sound separation of duties if it suits how you work.
  3. Add the ability to the role itself from Edit permissions. Careful: this changes the role's meaning for everyone holding it at every school, so do not do it for an individual case.

See the role catalogue for what each role is for, and Rejecting a registration with a reason for the effect of a rejection on the guardian.

What the reset button did, and how to get back​

The Reset to recommended defaults button changes nothing until you save, but saving it changes a great deal:

  • It 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. If you applied it and have not saved yet, leave the page without saving and nothing changes.
  • Once saved, it replaces the whole set. So anything not in the recommended set is removed — exactly what the preview lists under These capabilities will be removed.

What saving the recommended defaults removes today, from each role:

The roleThe abilities removed
SchoolAdminViewing certificates, issuing a certificate, withdrawing a certificate, refunding, and scheduling progress reports
ActivityAdminViewing certificates only
CoordinatorViewing certificates, and every activity-authoring ability: 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 — these roles already match the recommended set
TrainerNot applicable — there is no recommended set for this role, and the button refuses to work on it

And the button adds no ability to any role today, because no role is missing anything from its recommended set; so the effect is pure removal, and complete — which is why the preview and the table are read before saving, not after.

How to get back:

  1. Open Edit permissions for the same role.
  2. Grant the missing abilities again one by one from the same screen, comparing against the table above.
  3. Press Save changes, then ask those affected to sign out and back in.
  4. Do not apply the recommended defaults again while you are repairing it.
Do not guess what was lost

If you are not certain which abilities were granted before it was saved, contact support or a system administrator before granting them back by estimate. And note that scheduling progress reports does not appear in the permissions editor at all, so it cannot be restored from that screen and has to go to a system administrator.

The working rule: treat this button as a last resort on a role nobody uses, not as a tidying tool on a role your staff work with today. The detail is in Access best practices.


When to escalate to a system administrator​

These cases cannot be solved by any other role, however wide you make its permissions:

  • Resetting an administrator's password — the button appears for a system administrator alone, and nobody can read an existing password.
  • Correcting a guardian's email — no role holds this ability.
  • Managing partner integrations — no role holds this ability.
  • Creating or deleting a school — platform-level abilities that no school role holds.
  • Scheduling progress reports — it does not appear in the permissions editor at all.
  • Turning on the system switch for refunds before the refund button will appear.
  • Editing a built-in role's abilities if the Roles & permissions item does not appear in your sidebar.
  • Restoring abilities lost after a reset if you do not know which were lost.
A system administrator's permissions cannot be edited

On the roles screen, SystemAdmin appears tagged Full access (locked) with the edit button disabled, and a message saying it has full access and bypasses every permission check, so its permissions cannot be edited. See The system administrator's playbook.


Frequently asked questions​

I got an Access forbidden page with a permission name under the message — what do I do with it?​

That is the name of the missing permission. Copy it exactly as it is and send it to your school admin or a system admin; it is the same name shown beside the ability in Edit permissions, so they find it directly instead of guessing. And if the page says "This page requires ANY ONE of the following permissions:" with more than one name under it, any one of them is enough.

Why does the Access forbidden page sometimes show no name at all?​

Because the refusal was not about a missing ability but about the kind of account itself — opening a screen meant for trainers with an account that is not a trainer's, for example. There is no name to ask for; what is needed is the right account or role.

Why is the button missing altogether instead of disabled?​

Because the admin portal does not draw what the user has no ability for: the button is hidden rather than shown disabled. It means the role does not hold the ability at this school, or the person has not signed in since the last change. To be sure what each role holds, see the capability matrix.

I changed the role and nothing happened — what do I do?​

The change is saved, but the person's abilities have been loaded in their session since the moment they signed in. Ask them to sign out and back in, or wait for their session to refresh within about a quarter of an hour, and do not repeat the change. See Signing in and verification.

The cashier confirms payments but cannot approve a registration — why?​

Because the Cashier role is meant for the payments desk alone, and deciding registrations belongs to the roles that run the registration desk, such as Coordinator, ActivityAdmin and SchoolAdmin. If you need one person to do both jobs, add them a second role at the same school, because roles' abilities combine. See Approving a registration.

If you have not pressed Save changes yet, nothing has been saved: if the preview is still open, press Cancel; if you already applied it to the form, leave the page without saving. If you saved, yes, but by hand: grant the missing abilities again one by one from Edit permissions for that role, then save. If you do not know what was lost, do not guess — ask for help. See The system administrator's playbook.

A colleague says some permission-group headings show in English — why?​

Because four groups — Imports, Memberships, Certificates and Partners — have not had their headings translated yet, so they appear in English inside the Arabic screen. You will not see this yourself while the portal is in English. The ability names inside those groups are in Arabic and work like any other. See the capability matrix.

Where do I find the Reset password button?​

Under People > Admins, on the administrator's row, and it appears for a system administrator alone. A one-time password is created, copied immediately and handed to the member of staff. See Managing administrators.

The member of staff we removed can still get in — what is going on?​

They cannot sign in again, but their open session may last a few minutes until it refreshes, and there is nothing on the screens that ends it sooner. Signing out ends it immediately but is in their hands, so ask for it in a friendly departure and do not rely on it otherwise — and carry out the withdrawal as soon as the decision is made. See The staff access lifecycle.