> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aegissentinellab.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Staff ranks and Discord roles

> Configure priorities, explicit permissions and reviewed role delivery.

Open `/dashboard/{guild_id}/hierarchy`. A rank has a stable ID, editable name and description, priority, permissions, role bindings, optional capacity and promotion policy.

## Rank priority

Priority ranges from **1 to 10,000**; a smaller number is higher. Unranked members have priority 10,001. The actual Discord owner is a protected identity, not an editable rank. Naming a rank “Owner” does not grant owner access.

Across direct appointments and current Discord roles, the highest matching rank supplies authority. Equal highest priorities use their permission intersection. They do not combine permissions into a larger grant.

## Delegate explicit permissions

Native Discord Administrator alone grants no implicit AEGIS staff authority. Create a rank and bind the appropriate Discord roles or appoint the member.

| Work | Example permissions |
| - | - |
| Read server overview | `settings.view` |
| Edit preferences/scoring | `settings.edit` |
| Configure verification | `verification.configure` |
| Edit and publish rules | `rules.manage` |
| Configure protections | `security.configure` |
| Read/review reports | `report.view`, `report.review` |
| Accept/reject reports | `report.accept`, `report.reject` |
| Edit lower ranks | `staff.view`, `staff.permissions.manage` |
| Review/approve promotions | `promotion.review`, `promotion.approve` |
| Read audits | `audit.view` |

Reading a page and performing its actions can require different permissions. Editors cannot change the rank supplying their own authority, bind a role they hold, manage peers/superiors, or delegate permissions they do not possess.

## Choose Discord roles to grant

Use the role dropdown/search to select up to **25 roles**. Saving the rank defines the policy; it does not immediately assign roles to existing members.

**Grant all selected roles** assigns every missing bound role when an approved appointment/promotion is applied. New ranks default to this mode. Existing ranks keep their previous alternative-role behavior until explicitly changed: retain a bound role already held, or assign one in stable role-ID order.

Any bound role also recognizes its holder as a member of that rank. Role order, capacity, current ownership and approved permission snapshots are rechecked at delivery.

## Owner controls and recovery

Privileged appointments always require the actual owner's approval. Limits, emergency exceptions, approval-policy changes, Lockdown execution and the Anti-Nuke whitelist retain owner-only checks. A guild rank never grants global site-administrator access.

Failed role delivery is visible and can temporarily freeze the applicant's AEGIS management authority. Review a fresh reconciliation plan before retrying changed roles or ownership; do not assume a failed response means no role was applied.


## Related topics

- [Discord command reference](https://docs.aegissentinellab.com/en/commands.md)
- [Recruitment and promotions](https://docs.aegissentinellab.com/en/recruitment-promotions.md)
- [Rules and verification](https://docs.aegissentinellab.com/en/verification.md)
- [AEGIS Security Bot](https://docs.aegissentinellab.com/en/introduction.md)
- [Set up your server](https://docs.aegissentinellab.com/en/quickstart.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.