Staff ranks are Discord roles, on purpose
Axolix stores a staff member's rank as a Discord role ID rather than a label of its own. That one decision removes an entire category of sync problem.
- Product
- Design
Most dashboard tools that manage staff end up inventing a parallel set of ranks: a table of names and colours that has to be kept in step with Discord by hand. Axolix does not do that. A staff rank is a Discord role.
What that means in practice
A staff record stores the Discord role ID of the rank, not a free-text label. The names, colours and ordering shown in the dashboard are read live from Discord, so what you see in Axolix is what members see in the server.
- Rename a role in Discord and the dashboard follows, with nothing to re-sync.
- Colour a rank and it appears coloured in the staff list.
- Delete a role and the record is kept and marked as needing a new rank — the history is not thrown away with the role.
Permissions attach to ranks
What each rank is allowed to do is stored against the same role ID, as structured data rather than a pile of boolean columns. Adding a permission later means one key, not one migration per column.
The hierarchy rule
Because ranks are real roles with a real position in the server, Axolix can enforce a rule that matches how servers actually work: you cannot manage someone at or above your own rank.
That check runs on the server, on every change, not just in the interface. A manager cannot be edited by a staff member below them, whichever route is used to reach the record.
The honest caveat
Ranks being roles means the dashboard needs to know your server's roles, which requires the bot to be present and reachable. When Discord cannot be reached, the staff list still loads — it shows the records with rank names marked as temporarily unknown, rather than pretending the ranks were deleted.