Helios Rust Console Bot Documentation

Permissions & Roles

Permission model for owner, admin, and moderator command boundaries.

Page Summary

  • This page defines owner, admin, and moderator permission boundaries for Helios.
  • It is for server owners designing safe command access and escalation policy.
  • Use it as the source-of-truth matrix before enabling high-impact modules.

Related Product Pages

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

  1. Assign Administrator only to owner-level roles.
  2. Assign Manage Server to trusted admins.
  3. Keep moderators on read-heavy and support-focused commands.
  4. 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 Administrator unintentionally.
  • Admins lose Manage Server and 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 GroupMinimum PermissionRecommended Role
/server, /settings, /events, /economyManage ServerAdmin
/cmd, /tc, /bind, feed configManage ServerAdmin
/premiumAdministratorOwner
/wipeAdministrator + owner approvalOwner
Read-only monitoring (/whoson, /stats player)None or delegatedModerator