Skip to main content

The staff access lifecycle: from appointment to leaving

Goal​

To make one account's journey — from a member of staff's first day to the day they leave — a single story known in advance, rather than a judgement call made afresh every time. This page explains what happens at each stage, who carries it out, what actually changes in the system, and when the change takes effect.

The principle governing everything below is simple: the account is the person and their sign-in, the role is a bundle of abilities meaning the same thing at every school, and the scope is the branch at which the person holds that role. The role says what, the scope says where. The roles themselves are set out in the role catalogue.


The five stages​

StageWhat happensWho carries it out
1. AppointmentCreating the account or assigning an existing one to the branch, choosing the roles, and handing over a one-time passwordWhoever holds create/assign administrator — in practice SchoolAdmin or SystemAdmin
2. Change during serviceAdding or withdrawing a role, moving the person between branches, or running them at two branches at onceWhoever holds edit administrator
3. Making dormantMaking a trainer dormant at a school and reactivating them laterWhoever holds edit trainer
4. Ending accessUnassigning from a branch, or deleting the administrative account (disabling, not erasing)Deleting: whoever holds delete administrator or delete trainer — unassigning from a branch: whoever holds permission to edit the administrator's assignment
5. Returning or reappointmentReviving the same account with the same email, and issuing a new one-time passwordResetting the password: SystemAdmin only — and reviving with the same email is usually a SystemAdmin's step too, which a school administrator asks the support team for
Roles are general, assignment is particular

Editing one role's abilities changes its meaning for everyone holding it at every school. Assigning a role to a person changes that person alone, at that branch alone. Keep that distinction in mind at every stage below. See the capability matrix.


1. Appointment​

Reaching the screen: the sidebar > People > Admins, after choosing the school.

There are three paths to appointment, and the difference between them is the person's state before the appointment, not the kind of job they do:

a) Someone entirely new​

Press Add Admin, then fill in the required fields: first name, email address (which is the sign-in name for the admin portal), and at least one role from the Choose role drop-down. The mobile number is optional, and if you enter one, enter it without +966 and without the leading zero, beginning with 5 and 9 to 10 digits long.

If you choose SchoolAdmin, the phrase — full access appears beside it with a warning that the role grants full authority over this school and should be given only to a trusted school owner.

After Save, an Admin created panel appears with a one-time password.

b) Someone who is already an administrator at another school​

Do not create them a second account. Press Assign existing, search by name, mobile number or email (at least 2 characters), then Select, then set their roles at this branch, then Assign to this school. Anyone already assigned to your school appears with a disabled Already here button. This route is for a system administrator alone: its button appears to anyone who holds create/assign administrator, but its search works for a system administrator only; if you are a school administrator, ask the support team for the assignment through Help or request.

c) Someone with a non-administrative account (usually a guardian)​

Enter their email in Add Admin as usual. The system will stop and show This email already has an account with the account holder's name, and ask for explicit confirmation through Grant admin access.

The first, unconfirmed attempt changes nothing at all. After confirming, the person keeps their guardian sign-in (mobile number and verification code) and gains an administrative one-time password on top of it, and an Admin access granted panel appears. One person, one email, two faces.

The password appears only once

Copy the one-time password the moment it appears and hand it to the person directly; it will not appear again, and nobody — not even a system administrator — can read an existing password. The person will be required to change it at their first sign-in. The sign-in detail is in Signing in and verification.

A trainer is not created here

The add-admin list is built according to who opens it: a system administrator sees ten roles — the thirteen less SystemAdmin, Parent and Trainer — and the exclusion is enforced on the server, not only in the interface. A school manager sees nine and can assign all nine; SupportAgent is not shown to them at all, because the server will not accept it from anyone who is not a system administrator. A trainer is created from the Trainers screen — see Managing trainers — and a guardian is created when they register themselves.

The appointment steps in detail are in Adding and managing administrators.


2. Change during service​

Reaching it: a school administrator opens Edit Admin on the person's row and changes their roles at this branch there. A system administrator instead presses Schools & roles to open the Admin schools & roles page, which is the only way to see and change a person's roles across several branches, and which no other role can open. A card appears for each school they work at, and each card has a Roles in this school section shown as chips, with Add a role… and a Save roles button belonging to that card.

What you wantWhat you do
Add an ability for one personAdd a second role on their school's card — do not edit the role itself
Withdraw an abilityRemove the role's chip from the card, then save
Move them between branchesAdd them to the new branch first, then unassign them from the old one
Run them at two branches at onceKeep two cards open with different roles — each branch has its own roles and its own save button

A person's abilities at a branch are the union of their roles at that branch. Abilities accumulate and do not cancel one another, so no role "subtracts" from another. Which is why the safe way to give someone one extra ability is to add them a second role, not to edit the role bundle everyone shares.

And the scope is entirely separate: a person may be SchoolAdmin at one branch and Finance at another, and cannot read the data of a branch they are not assigned to even if they hold the same role name elsewhere — and the check happens on the server with every request.

Disabling Save when the roles are emptied is intended

If you remove every chip from a school's card, the Save roles button is disabled and a message appears asking you to choose at least one role or unassign the administrator from this school. That is not a fault — the system prevents a person being assigned to a branch with no role, and requires you to decide explicitly: either a role, or out of the branch.

The operational detail is in Assigning administrators' roles per school.


3. Making dormant​

Trainers alone have a middle state between working and gone:

  • On the Trainers screen a trainer appears as Active or Dormant.
  • Make dormant stops them temporarily, and Activate brings them back.
  • The action is reversible, keeps the record, and concerns the current school alone — the trainer's work at other schools is unaffected.
  • There are bulk actions for archiving and activating in the trainer list, for when it happens to a group.
  • Delete on a trainer is the permanent option, so do not use it for a temporary absence.

Administrators, by contrast, have no dormant state. If you need to pause an administrator, the practical equivalent is one of two things: withdraw the role you want to stop and leave a lesser one, or take them out of the branch and reassign them later. The second is not the school's to do alone: reassigning is a system administrator's step, because a school administrator most likely cannot add back someone they deleted. And read Ending access first: if that was the person's last branch, their administrative account is disabled entirely. See Managing trainers.


4. Ending access​

There are two different actions, and they are often confused:

The actionWhere it livesWho can use it
DeleteThe Admins list, inside a schoolA school administrator, at their own branch
Unassign from schoolSchools & roles, on a branch's cardA system administrator

Both follow the same rule, and it depends on how many branches the person works at:

How many branchesWhat happens
More than oneThat branch's link and its role assignments are removed. The person stays an active administrator at their other branches, and their session is left alone.
This was the last oneThe administrative account is disabled entirely, its assignments are deactivated and its session is ended.
So "I deleted them" does not mean "their access is gone"

For someone working at two schools, deleting them at yours removes them from yours alone — they carry on at the other, with the session they already have. If what you need is their access ended everywhere, every branch has to be dealt with, and a system administrator is the only one who can see them all.

Three facts complete the picture:

  1. Deleting is disabling, not erasing. The history is kept, and a system administrator can later revive the same account by adding the same email again, rather than creating a new one, and every session it has open is then ended. Usually its old password stops working and a new one-time password is emailed to the person, but in some cases the old one is kept — so read the warning in Returning or reappointment before bringing back any account that was stopped for a reason. A school administrator, by contrast, most likely cannot do this themselves: after the delete the add form refuses the email, so they ask the support team to bring the person back through Help or request.
  2. Ending access concerns the administrative face alone. Disabling the administrative side disables neither the guardian side nor the trainer side of the same person; a guardian who was an administrator carries on signing in to the parents app as usual.
  3. An open session may hold on for a little while. After Delete — or after unassigning from the last branch — the person cannot sign in again and their saved session is void, but a session open right now may continue for a short time. See the next section.
Know which of the two is about to happen before you confirm

Both actions ask you to confirm, but the two messages do not say the same thing. The confirmation for Unassign from school — a system administrator's action — changes with the person's situation: if they work at other branches, it says they will be removed from this school only and their other schools are unaffected; if this is their last, it says so by name: unassigning here does not just remove them from a branch, it disables their whole admin account and ends their session, and they can be restored later by re-adding the same email.

The confirmation for Delete inside a school shows one fixed warning instead: if this is the person's last school, the delete disables their whole admin account and ends their session, and either way you may not be able to add them back yourself afterwards. It does not tell you whether that is their case, so if you are a school administrator, ask a system administrator how many branches the person works at before you delete. And there is no one-press undo either way.


5. Returning or reappointment​

A member of staff returning is not a fresh start:

Read what the card says about the password before you do anything else

Adding them again with the same email revives the account and ends every session it has open in the same step. No password is shown on screen afterwards. Instead a card titled Admin re-added appears — or School admin re-added when they were added from the school admins screen — saying what happened to their password, which is one of three things:

  • A one-time password was emailed to them — the usual case: the old password no longer works, the new one is in their inbox, and they are asked to change it at first sign-in. So do not reset their password afterwards: that invalidates the password that was just emailed, and the person receives an email with a password that no longer works.
  • It could not be sent: the old one no longer works, and the new one could not be emailed to them, so they cannot sign in yet. Here a system administrator issues a new password with the Reset password button.
  • The old password was kept: the old one is left unchanged only when this sign-in is used for more than admin access at this school, and it works again as soon as they are back. In the ordinary friendly return — the same person coming back to their job — it is their own password and nothing more is needed. But if the account was stopped for a reason, or there is any chance its old password is known to somebody other than its owner, a system administrator should issue a new password immediately with the Reset password button.

Which of the three will happen is not known in advance. So if the account was stopped for a reason, do not re-add it yourself. Escalate it: ask a system administrator to do the re-adding, then the reset straight away if the card says the old password was kept, so nobody has to hold the window between the two steps open waiting on another person. And do not park the account on a narrow role while it waits: SupportReadOnly is not a safe holding place — it writes nothing, but it still shows students' names and statuses in registrations, the waiting list, attendance and search.

The detail is under What you should end up with in Adding and managing administrators.

  1. They are added with the same email address they used before. The system revives the same account with its record, does not create a duplicate, and ends every session it has open at this step. This step is usually a system administrator's: after the delete, the add form refuses the email for a school administrator, unless the person still has another link to the school, such as being the parent of a student there or an active trainer there. If you are a school administrator, ask the support team for it through Help or request.
  2. Read the card that appears after saving, act on what it says about the password as in the warning above, then press Done.
  3. Reassign them to the branch you want and choose their roles there — do not assume their old roles came back as they were; check the branch card yourself.
  4. Only when needed — if the password could not be sent, or the old one was kept and there is a reason it should stop working — issue a new one-time password from the Reset password button on the person's row, which only a system administrator sees. The action is confirmed with a message asking whether to reset the password for that email, saying a new one-time password will be created. This step invalidates any earlier password, including one that was just emailed to them, so do not carry it out if the card says one was emailed.
  5. As always: it appears once, it is copied immediately, and it must be changed at first sign-in.

If you are not a system administrator you will not see this button, and that is expected — ask whoever holds it to reset it. See The system administrator's playbook.


When each change actually takes effect​

A person's abilities are loaded into their session at the moment they sign in, and the screens then work from that. This is the nature of sessions rather than a fault in the system, but it means a consequence you have to plan for:

  • Any change — adding a role, withdrawing a role, or editing the role bundle itself — does not appear to the person in the session they have open right now.
  • The change takes effect at their next sign-in, or when their session refreshes, which in practice is within about a quarter of an hour at most.
  • And it takes effect immediately if the person signs out and back in.

The system says so itself on both screens: after saving permissions, a message says the changes take effect at the affected administrators' next sign-in (or when their session refreshes); and after saving roles, that the roles were updated and the changes take effect at the administrator's next sign-in.

An urgent removal — face the truth as it is

Carrying out the action prevents a new sign-in immediately and ends the saved session. But the session open on the person's device at that moment carries on working until its own time runs out.

Voluntarily signing out is not a security guarantee. It closes the window immediately only if the person is co-operating; and somebody whose access is being removed in unfriendly circumstances can simply not do it. And there is no button on the admin screens today that ends an open session on the spot.

So, in any unfriendly removal:

  1. Carry out the removal immediately — every minute of delay adds to the window rather than reducing it.
  2. Assume the person may remain inside the system for a few minutes after the action, and that they may see whatever their abilities allowed during that time. Plan for that rather than assuming the opposite.
  3. If their abilities covered sensitive data or financial actions, tell a system administrator immediately so they can follow it up and review the record of what happened; do not simply carry out the action alone.
  4. Do not tell the person when their access will be removed before you remove it.

Ask them to sign out afterwards as a useful extra step in a friendly departure — not as a measure you rely on.

Against that, remember that screens and buttons are hidden rather than disabled. So "the button is not there" usually means: this role does not hold this ability at this school, or it does and they have not signed in again yet. See Troubleshooting access.


A quick checklist​

On appointment​

  1. Search for the person under Assign existing before creating any new account, to avoid a duplicate — its search is for a system administrator alone, so if you are a school administrator, ask the support team through Help or request.
  2. Enter the first name and email address, and the mobile number — if there is one — beginning with 5, without +966 and without a leading zero.
  3. Choose the fewest roles that genuinely cover their work, and do not choose SchoolAdmin except for a trusted school owner.
  4. Make sure you are working inside the right branch before saving, because the assignment belongs to the branch, not to the whole system.
  5. Copy the one-time password and hand it to the person directly before closing the panel.
  6. Ask them to sign in and change the password, and check with them that the screens you expect are showing.

On leaving​

  1. Find out how many branches they work at before pressing anything — from Schools & roles if you are a system administrator, or by asking one if you are not.
  2. Decide explicitly: out of one branch, or administrative access ended completely.
  3. Read the confirmation, and know what it does and does not say: the Unassign from school confirmation names which of the two is about to happen — removal from this branch alone, or the whole account disabled because this was the last one. The Delete confirmation warns about the last-branch case without saying whether it is theirs, which is why step 1 comes first.
  4. If the absence is temporary and the person is a trainer, use Make dormant rather than Delete.
  5. For an urgent removal, carry out the withdrawal first and immediately, and reckon on their open session lasting a few minutes — asking them to sign out helps only in a friendly departure and is not to be relied on otherwise.
  6. Check that their other face (guardian or trainer) still works if it is needed, and hand their duties to somebody who holds the abilities for them.

Common situations and mistakes​

  • Save roles is disabled and I do not know why: you removed every chip from the card. Put at least one role back, or use Unassign from school if what you meant was to take them out of the branch.
  • I deleted the administrator, then tried to add them again, and got the message "This e-mail belongs to an account outside this school, so it cannot be added here…": that is expected — the delete ended their link to your school, so the form accepts their email only if they still have another link to it. Ask the support team to bring them back through Help or request. When a system administrator brings them back with the same email, the same account is revived with its old record, because deleting is disabling rather than erasing.
  • I unassigned them from a branch and all their access vanished: that was their last branch, so their administrative account was disabled entirely. Reassign them to a branch and choose their roles there.
  • The member of staff says nothing changed after saving: their session still carries their old abilities. Ask them to sign out and back in.
  • I deleted a guardian's administrative side and they complained… or did not: the guardian side is unaffected and their sign-in to the parents app stays as it was; if you meant to stop their guardian account, that is an entirely different action.
  • I cannot find the Reset password button: the button is for a system administrator alone; ask them to issue a new one-time password.
  • The one-time password was lost before it was handed over: it cannot be recovered or read. The only way is to issue a new one through a reset.

Frequently asked questions​

What is the difference between unassigning from a school and deleting?​

Not what the names suggest. They are the same operation reached from two screens: Delete on your own branch's Admins list, and Unassign from school on a branch's card under Schools & roles, which only a system administrator can open. Both take the person out of that branch alone while their other branches carry on — and both disable the whole administrative account, and end the session, when it was their last branch. So the question that decides the outcome is not which button you pressed but how many branches they work at. The Unassign from school confirmation tells you which case you are in, while the Delete confirmation warns about the last-branch case without saying whether it is theirs — so ask a system administrator before you delete. See Assigning administrators' roles per school.

I removed the member of staff and their session is still working — why?​

Because their abilities were loaded into their session when they signed in, and carry on until the session refreshes — in practice within about a quarter of an hour. They cannot sign in again. Signing out closes the window immediately but it is in their hands, so do not rely on it in an unfriendly removal: carry out the withdrawal immediately, and if their abilities touched sensitive data or financial actions, tell a system administrator to follow it up. See Troubleshooting access.

Can I pause an administrator the way I do with a trainer?​

No, the dormant state exists for trainers only. The equivalent for an administrator is withdrawing the role and leaving a lesser one, or unassigning them from the branch and reassigning them later — and reassigning is a system administrator's step, because a school administrator most likely cannot add back someone they deleted. See Managing trainers.

A member of staff has come back after a while — do I make them a new account?​

No. They are added with the same email and the same account is revived with its record, then reassigned with their roles at the branch you want. That adding is usually a system administrator's step, because the add form refuses the email for a school administrator after the delete; if you are a school administrator, ask the support team for it through Help or request. After the adding, an Admin re-added card says what happened to their password: usually the old one stops working and a new one-time password is emailed to them, and the old one is kept only when this sign-in is used for more than admin access at this school. In that case — if there is a reason it should stop working — or if the email could not be sent, a system administrator issues a new password with the Reset password button. See What you should end up with in Adding and managing administrators.

I want to give them one extra ability — do I edit the role?​

Do not edit the role — editing it changes its meaning for everyone holding it at every school. Add them a second role on their school's card; their abilities at the branch are the union of their roles there. See the capability matrix.

Where do I find all the branches a person works at?​

From the person's row under Admins, a system administrator presses Schools & roles to open Admin schools & roles, with a card for each branch. It is the only screen that shows them all, so if you are a school administrator, ask a system administrator before any removal. See Access best practices.

Why is there no Trainer option in the add-admin list?​

Because the add-admin list never shows Trainer, to a school manager or a system administrator alike; a trainer is created from the Trainers screen, and the exclusion is enforced on the server so it cannot be worked around. See the role catalogue.