Access & Permissions
Control organization dashboard access and which Discord roles can use staff commands.
GotNext separates organization web access, Discord command permissions, and billing ownership. A person can have access to one without automatically receiving either of the others.
Web Dashboard Access
Every newly connected Ranked Queues server belongs to an organization. Organization member roles are authoritative for access to its web dashboard.
| Organization permission | Web dashboard capabilities |
|---|---|
| Manage Ranked Queues | Operate queues, players, matches, seasons, achievements, and related activity. |
| Manage Discord | Full Ranked Queues administration, server settings, and Discord command permission setup. |
| Neither | No access to the organization's Ranked Queues server dashboard. |
Organization owners and staff with the appropriate organization member-management permission add people and assign roles from the organization's People area. The Ranked Queues Access & permissions page links back to that workspace instead of maintaining a second list of dashboard users.
A staff member does not need to link a personal Discord identity to use the web dashboard. Their signed-in GotNext account and organization membership determine access. Discord authorization is still required during a new install so GotNext can verify Manage Server. Assigning an existing standalone workspace to an organization is restricted to the current Discord server owner.
Billing stays protected
Organization permissions do not grant access to another person's Stripe customer portal. The organization billing owner controls the current GotNext subscription. An existing paid Elo Bot subscription remains restricted to its original purchaser or current entitlement owner. Contact GotNext support if subscription ownership needs to be transferred.
Older standalone servers
An existing server that has not yet been moved into an organization continues to use verified Discord ownership and its saved Viewer, Moderator, or Administrator grants. This is a compatibility path, not the setup model for new servers. When the server is claimed again, the flow asks the current Discord server owner to choose an organization and preserves the server's queue, player, rating, and match data.
Web dashboard access does not change what a member can do with slash commands inside Discord. Configure that separately with Discord role permissions below.
Discord Command Permissions
Discord Administrators can use staff commands. Everyone else gets command access through role permissions you assign in the Elo Bot dashboard.
- Admins bypass staff command checks: Members with Discord Administrator can use staff commands automatically.
- Hidden membership stays explicit: Seeing names in a hidden queue requires a role with View hidden queue, including for Discord Administrators.
- Roles receive permissions: Add a Discord role, then grant only the bot permissions that role should use.
- Permissions unlock command groups: Each permission maps to a clear set of slash commands.
Permission Groups
Start with Report results for match staff. Add Manage players for dispute staff, Manage queues for setup owners, and View hidden queue for operators who only need visibility.
REPORT_RESULTS
Close matches and correct reported outcomes without giving broader server control.
Best for: Trusted match reporters, referees, and moderators who watch active matches.
| Command | What it unlocks |
|---|---|
/win | Report the winning team and optionally award MVPs. |
/cancel-match | Cancel an active match before ELO changes apply. |
/void-match | Void a completed match and reverse ELO changes. |
/overturn-match | Flip the winner of a completed match. |
/unvoid-match | Restore a voided match and reapply ELO. |
/mvp | Award MVP bonus ELO after a match. |
/revoke-mvp | Remove an MVP award and reverse bonus ELO. |
/close-match | Close a reported match's dedicated channel. |
/flawless | Award the configured Premium flawless bonus. |
/revoke-flawless | Remove a flawless bonus from a completed match. |
/trade | Swap two active-match players between teams. |
MANAGE_PLAYERS
Handle player account issues, rating corrections, and queue bans.
Best for: Moderators who resolve player disputes but should not change queue setup.
| Command | What it unlocks |
|---|---|
/set-elo | Manually set a player's ELO. |
/rename-player | Set a custom display name for a player. |
/remove-player | Unregister a player from the ELO system. |
/ban-player | Ban a player from queues. |
/unban-player | Remove a player's ban. |
/ban-status | Check a player's current ban status. |
/force-join | Add a registered player to a queue. |
MANAGE_QUEUES
Create queues, tune match behavior, configure maps, and manage seasons.
Best for: Server owners and senior staff responsible for the competitive setup.
| Command | What it unlocks |
|---|---|
/setup | Create or reconfigure a queue. |
/freeze-queue | Pause or resume new joins. |
/clear-queue | Remove all waiting players. |
/remove-from-queue | Remove one waiting player. |
/queue-board | Enable or disable the persistent queue board. |
/cancel-draft | Stop an active captain draft. |
/sub | Substitute a player in an active match. |
/trade | Swap two active-match players between teams. |
/cancel-match | Cancel an active match. |
/uncancel-match | Restore a cancelled match. |
/undo-match | Reopen a completed match for corrected reporting. |
/cancel-unscored-matches | Bulk-cancel old unresolved matches. |
/set-maps | Configure the map pool. |
/set-map-mode | Set random or vote-based map selection. |
/set-captain-mode | Choose how draft captains are selected. |
/set-autoping | Ping a role when the queue is almost full. |
/set-mvp-bonus | Set the bonus per MVP award. |
/set-flawless-bonus | Set the Premium flawless-victory bonus. |
/flawless | Award the Premium flawless bonus. |
/revoke-flawless | Remove a flawless bonus. |
/streak-bonus | Configure win-streak milestone bonuses. |
/matchmaking | Select Standard or Premium Skill Range matching. |
/elo-gate | Limit a queue by player rating. |
/set-challenges | Configure direct challenges and maximum wagers. |
/season-reset | End the current season and reset ratings. |
VIEW_HIDDEN_QUEUE
Inspect anonymous queue membership without granting queue configuration access.
Best for: Queue operators who monitor hidden queues but should not edit queue settings.
| Command | What it unlocks |
|---|---|
/queue | Show who is waiting when the queue hides names from regular players. Everyone can still see queue counts. |
Discord Administrator server settings
The following server-wide commands are limited to Discord Administrators. They are not assignable through the four-column role-permission grid.
| Command | What it changes |
|---|---|
/set-starting-elo | Starting rating for new registrations. |
/set-provisional-threshold | Games required before a rating is established. |
/set-scores-channel | Default Discord results channel. |
/set-tier-announcements | Rank-promotion announcements. |
/season-config | Season duration, reset rules, summary, and decay. |
Set Up Role Access
The dashboard editor saves a Discord role to permission map for each server. If a role was created after the page loaded, refresh the role list before adding it.
- 1
Open your Elo Bot server dashboard
Navigate to your server in the dashboard. - 2
Go to Access & permissions
Select the Access & permissions tab for that server.
- 3
Add a role
Use Add role to pick a Discord role. If a new role is missing, use Refresh roles.
- 4
Toggle permissions
Turn on the exact permissions that role should receive. - 5
Save changes
Save before leaving the page.
Recommended first pass:
- Give moderators Report results.
- Keep Manage queues limited to senior staff.
- Give queue monitors View hidden queue, including administrators who need to inspect hidden names.
Example Setup
This is a common split for communities where moderators handle match flow but only a few people own queue configuration.
| Role | Report results | Manage players | Manage queues | View hidden queue |
|---|---|---|---|---|
| @Admin | Automatic | Automatic | Automatic | Automatic |
| @Moderator | Yes | Yes | No | Yes |
| @Queue Operator | No | No | No | Yes |
| @Match Reporter | Yes | No | No | No |
| @Everyone | No | No | No | No |
- Admins can do everything automatically through Discord Administrator.
- Moderators can report results, manage players, and inspect hidden queues.
- Queue operators can inspect anonymous queues without editing queue settings.
- Regular members only use player commands like
/registerand/join.
Discord Role Hierarchy
Discord still controls what the bot can edit. Put the GotNext Bot role above player and moderator roles so nickname updates and rank tier role assignment can work.
Role order: Go to Server Settings > Roles, find the GotNext Bot role, and drag it above the player and moderator roles it needs to manage.
Nickname limit: The server owner's nickname cannot be changed by any bot. This is a Discord limitation, even when role order is correct.
Two-factor authentication: If your server requires 2FA for moderator actions, the bot owner's Discord account also needs 2FA enabled before role and nickname operations can work.
Re-inviting the bot: If permissions are missing, re-invite the bot from the dashboard. Re-inviting updates the bot's Discord permissions without removing it from the server.
If nickname or role updates silently fail, check role order first. The bot can only manage users and roles below its highest Discord role.
Team Voice Room Permissions
Optional Team Voice Rooms use Discord channel permissions separately from the dashboard's staff command permissions.
- Manage Channels creates and removes the temporary Team 1 and Team 2 rooms.
- Manage Permissions limits each room to the correct players and configured match-channel roles.
- Connect allows the bot to manage voice-room access.
- Move Members is only used when the server owner enables automatic moving.
The standard GotNext invite requests these permissions. A category-specific deny can still override the server role, so confirm the GotNext Bot role has access in the category selected under Match Channels.
Automatic moving only affects players who are already connected to voice when the match starts. Players who are not connected join through the buttons in the private match channel.