Ranks and permissions

Each service has its own hierarchy of ranks, from highest to lowest, and each rank has its permissions. Ranks are managed in Settings › Ranks & permissions (administrators) or in a service’s Ranks module (members whose rank allows it). Every permission is described on the Permissions page.

The police hierarchy and the selected rank’s matrix

Picking the service

At the top of the page, pick the service by its short name (for example LSPD, EMS, DOJ). Beyond four services, and on a phone, a Service drop-down replaces the tabs. The page then shows its Hierarchy on the left and the selected rank’s Permissions on the right. With no service at all, the page first invites you to create one.

The hierarchy

Each action has its own permission (Ranks module):

• Add a rank (Ranks › Create a rank): give it a name and, if you also have Ranks › Edit permissions, choose its Starting permissions (No permissions or Same as an existing rank), then Create rank. The new rank lands at the bottom of the hierarchy. A service has 40 ranks at most.
• Rename (Ranks › Rename and reorder): click the rank’s name in the hierarchy and edit it (up to 40 characters); Enter or clicking elsewhere saves.
• Reorder: drag a rank by its handle, or use its move up / move down buttons (administrators only).
• Delete (Ranks › Delete a rank): select the rank, then hold down the Delete button above its matrix. Deletion is refused while members still hold the rank: reassign them first. The deleted rank moves to Archives, where an administrator can restore it.

A button you are not allowed to use stays visible, locked with a padlock, naming the permission you would need (see Hidden or locked).

The permission matrix

Click a rank to show its permissions (you need Ranks › Edit permissions to change them).

Screenshot coming soonpermissions-matrix

The matrix: domains, collapsible modules, search, filter and counters

• Permissions are sorted by domain (Operations, Records, Staff, Department), then by module enabled in the service. Click a module to expand it, or Expand all.
• Each permission has a clear label and a short help below.
• Whole group ticks or unticks every permission of a module.
• Each module shows its counter (for instance “3/6”); at the top, the overall counter reads for instance “60 of 160 granted”.
• Search a permission finds a box by a word (“revoke”, “fine”); the filter shows All, Granted or Not granted.
• Copy from… takes over another rank’s permissions at once. Permissions you don’t hold yourself stay as they are on the rank.
• Game-related permissions (licenses, players, plate reader…) only show with the game integration. Only the modules enabled in the service appear in the matrix.
• On a phone, the Rank shown list picks the rank whose matrix you see.

Each box is saved as soon as you tick it: the indicator goes from “Saving…” to “Saved”. Discipline and summons are personal modules: everyone always sees what concerns them, even without the permission to see the whole service’s. Likewise, everyone sees their own payslip and hours. Administrators always have every permission.

Rules that protect the hierarchy

You only manage lower ranks, and only give what you have

A member with permissions on ranks, who is not an administrator:

• can only edit, rename or delete ranks strictly below their own; their own rank is marked Your rank, and the ones above are locked;
• can only grant or remove permissions they have themselves: other boxes in the matrix are locked.

Nobody can promote themselves. The organization’s administrators are not bound by these limits.

The same rule applies to the roster: someone who assigns or removes a service’s members only acts on members ranked below them.

The Ranks module

Enabled in a service, the Ranks module (in the Staff group) opens the same editor for that service only. With Ranks › See ranks, you see the hierarchy and permissions Read-only; each other permission of the module opens its own action, within the limits above.