Help / People & time off

Systems access

Systems access is a checklist on every profile: one tick box per system — Google Workspace, GitHub, your password manager — saying whether that person has been given access.

It is a record you keep by hand. Ticking a box does not grant access, and clearing one does not remove it. Nothing here is connected to the systems themselves, so it is only as accurate as the last person who updated it.

Switching it on

It is off until an HR admin switches it on.

  1. Open Settings, then Systems access. (There is also a Set up systems access button at the top of the list in People.)
  2. Tick Show systems access on profiles.
  3. Add each system you want to track under Systems.

Switching it off again hides the section and keeps everything recorded, so nothing is lost if you switch it back on.

The list of systems

On Settings → Systems access each system shows how many current people are marked as having it.

  • Add systems takes one name or many: one per line, or separated by commas. Anything already on the list is skipped and named, and the rest are still added. Each new system puts an unticked box on every profile.
  • Rename changes the label everywhere and keeps the ticks.
  • Remove takes the system off every profile. What was recorded is kept but no longer shown.

Sub-systems

A system can have sub-systems under it — a client's GitHub organization under GitHub, say. To add new ones, choose the parent in Add under below the list, then add the names the same way.

  • Sub-systems go one level deep.
  • Each is its own box, shown indented under its parent on every profile.
  • Wherever one appears on its own — the offboarding list, the assistant — it is named with its path, GitHub › Northwind.
  • Ticking a sub-system does not tick its parent for you.
  • Removing a parent removes its sub-systems too.

Arranging the list

Drag a system by its handle (⠿) to rearrange the list. Where you drop it decides what happens:

  • Between two systems puts it there. Dropped between sub-systems, it becomes one of them.
  • Onto a top-level system puts it underneath, as that system's last sub-system. Drop GitHub B onto GitHub A and it becomes GitHub A › GitHub B.
  • On the dashed space at the end of the list takes it out to the top level, last.

A line or an outline shows where it will land before you let go. Where a drop is not allowed, the outline is dashed and the reason is written under the list:

  • a system that has sub-systems of its own cannot go under another, because sub-systems go one level deep;
  • two systems with the same name cannot share a parent.

A top-level system takes its sub-systems with it when it moves. The new order is the order on every profile, on the People export and in the API.

Without dragging. Every row has a Move… menu that does the same from the keyboard or a phone: Move up, Move down, Move to the top level, and Move under each system it can go under. It only lists moves that are allowed.

Moving a system changes where it sits, nothing else: who is marked as having access is kept, and its path changes everywhere it is named.

Two systems side by side cannot share a name, whatever the capitalization; the same name under two different parents is fine. The list holds up to 200, sub-systems included.

Recording access

Open a person in People and choose the Systems access tab. It appears once systems access is switched on. Tick a box when they have been given access; clear it when it has been taken away. Each box saves as you click it and shows when it last changed and who recorded it.

You can do this for somebody with no profile yet — a new starter's accounts are usually set up before they have filled anything in.

Several people at once

On Settings → Systems access, People on a system's row lists everyone with a box each, ticked for whoever has it now. Tick and clear as many as you like, then Save. Only the boxes you changed are recorded, so everyone else keeps their own date and "recorded by". People who have left are listed separately, so clearing their access at offboarding can be done from the same place.

Offboarding

When somebody has been archived and still has boxes ticked, their profile says so, and Settings → Systems access lists them under Left, and still marked as having access with the systems outstanding. Offboarding is finished when that list is empty.

Archiving somebody does not clear their boxes for you. That is deliberate: a box should be cleared when the access has actually been removed, not when the person was archived.

Who can see and change it

HR admins only. Nobody else sees the section, on their own profile or anybody else's, and the assistant will not report it to them.

Asking the assistant

The assistant can tell an HR admin who is recorded as having access to what, and who has left with boxes still ticked. An HR admin can also ask it to tick or clear a box, for one person or several at once — name a sub-system by its path, "GitHub › Northwind". It updates the record only, the same as the page. It can also move a system under another top-level system, or out to the top level ("put GitHub B under GitHub A"), by the same rules as dragging. Adding systems to the list, and reordering within a level, are done on the page.

Updated 2026-10-08. Still stuck? Contact support or return to the Help Center.