Permissions
Who can use what, and how it's decided.
The basics
Marin checks permissions every time someone uses a command or a button. Hiding a button isn't enough: if the person doesn't have permission, Marin won't do it.
Server administrators can use almost everything. For everyone else, you choose which roles can do what in /setup.
Access levels
| Level | Who has it | Commands |
|---|---|---|
| Any member | Anyone in the server who can post in the channel. | |
| Score reporters | Administrators and the roles you pick in /setup → Score. If you pick none, only administrators. | |
| Leaderboard managers | Administrators and the roles you pick in /setup → Leaderboard. | |
| Rank managers | Administrators and the roles you pick in /setup → Ranking. The module has to be set up. | |
| Moderators | Administrators always. Otherwise, the role you assign to that command in /setup → Moderation or, if it has none, the general moderation roles. | |
| Administrators | Anyone with Discord's "Administrator" permission. | |
| Security: view only | Administrators. They can see status, incidents and diagnostics, but can't change anything. | |
| Security Manager | The server owner and anyone with a Security Manager role, which only the owner can assign. | — |
| Server owner | The account Discord marks as the server owner. It's the only one that can appoint Security Managers. | — |
How Moderation decides
- Are they an administrator? Allowed.
- Does the command have its own roles? Only those roles can.
- Otherwise, do they have one of the general moderation roles? Allowed.
- If no role is configured, or they were deleted, the command says so plainly so an administrator can fix it.
>role is the exception: it always requires being an administrator and can't be delegated.
Marin Security
Security has its own levels, because its actions are sensitive. Administrators can see status and incidents. Security Managers can change settings and restore. Only the server owner can appoint Security Managers.