Everything a user may do comes from the permission group on their record.
This screen defines those groups.
Where: Admin → General settings → Privileges · Permission:
adminPrivileges
Title Privilege groups, with counts of groups, assignments and modules. Chips
filter to All, No users, With manuals or Archived; sort by name,
users or manuals; search by group name. The bottom bar has New group and
Export matrix.
The editor opens as a drawer with three tabs: Details, Users and
Manuals.
Under Details: the Group name, a Filter modules… box, a
Set all rail, and a running tally of N editable · N view only · N denied.
Modules are grouped into Flight operations, Crew, Crew app,
Maintenance, Reports, Administration and Other.
| Level | Means |
|---|---|
| DENY | Not available |
| VIEW | Can see, cannot change |
| EDIT | Can see and change |
Not every module offers all three; switches a module does not support are
disabled.
admin gain some privileges automatically. CertainThe
/adminhub labels tiles Editable / View only / No access, but the
labels do not block navigation — a tile can be opened even when marked no
access. The real enforcement happens on the server, which refuses the action.
So a user may reach a screen and find it empty or their save rejected. Judge
permissions by this screen, not by whether a page opens.
| Symptom | Cause | Fix |
|---|---|---|
| A user opens a page but it is empty | The route is not gated; the server refuses the data | Grant the privilege here |
| Changes save but do not persist | The privilege for that specific area is missing | Grant the matching …Manage… privilege |
| An admin group has privileges nobody set | Some privileges follow the admin level | Expected |
| A tile always says "No access" | Its declared privilege no longer exists | Cosmetic; judge by this screen |