Helios Documentation Portal
Permissions & Roles
Permission model for owner, admin, and moderator command boundaries.
Overview
Most Helios admin commands require Manage Server. Premium and destructive workflows should be restricted to Administrator owners.
Who This Is For
- Owners defining policy
- Admins implementing command access
Requirements
- Ability to edit Discord role permissions
- Clear owner policy for premium and wipe actions
Setup
- Assign
Administratoronly to owner-level roles. - Assign
Manage Serverto trusted admins. - Keep moderators on read-heavy and support-focused commands.
- Validate with test accounts before launch.
Commands or Controls
/server list
/settings server
/premium status
/wipe bags
Example Use Case
Owner keeps /premium and /wipe workflows restricted to two trusted accounts while admins run day-to-day operations.
Common Issues
- Moderators receive
Administratorunintentionally. - Admins lose
Manage Serverand cannot configure feeds or settings. - Staff policy exists but does not match real role permissions.
Tips / Best Practices
- Audit role permissions every wipe cycle.
- Keep a test account for permission validation.
- Log all destructive actions in
#helios-audit.
Permission Matrix
| Command Group | Minimum Permission | Recommended Role |
|---|---|---|
/server, /settings, /events, /economy | Manage Server | Admin |
/cmd, /tc, /bind, feed config | Manage Server | Admin |
/premium | Administrator | Owner |
/wipe | Administrator + owner approval | Owner |
Read-only monitoring (/whoson, /stats player) | None or delegated | Moderator |