Roles
Permission-based roles — fine-grained matrices controlling exactly what holders can view and do.
What it is
Roles define what people are allowed to do in the system. Shown as a card grid, each role is a matrix of fine-grained permissions controlling exactly what its holders can view and do — from reading flight records to editing pricing rules. Assigning a user a role is how you decide their reach.
These permissions are not cosmetic: every UI control and every server action is gated by them, so the controls a user cannot use simply do not appear, and the actions they are not allowed to take are refused on the server too. Roles that fall out of use can be archived or deactivated rather than deleted, keeping the history intact. Open an individual role to inspect and adjust its permission matrix.
When editing a role, the permission matrix is organised into groups by area (flights, members, aircraft, reservations, transactions, roles, users and more). Most areas have a View and a Manage pair, and some carry additional standalone permissions — for example approving flights or duties, permissions tied to record ownership (marked with a label), or assigning roles. Granting Manage automatically includes the matching View (it appears ticked and locked).
How to use it
- Browse the card grid — scan all roles and the access each one grants.
- Open a role — review and edit its permission matrix at
/roles/[id]. - Tune permissions — grant only what a role needs; unavailable controls disappear for its holders.
- Archive unused roles — deactivate roles you no longer assign instead of deleting them.