1) Status — check connection health & server state

What it is

• A single-pane view to inspect the bot’s live health, per-server connection diagnostics, and recent runtime activity. It shows whether the dashboard connection is complete or needs review, bot authorization state, last sync time, and a list of connected servers and any servers that need attention.

Where to look

• Open Dashboard → Status in the left navigation (Status is the first Dashboard page).

How to use it

1. Health overview — At a glance you’ll see:

   • Active bot status (Complete / Review required), the currently tracked bot, and an authorization status (e.g., “Pending invite / permissions”).

   • Last sync timestamp so you know how recent the dashboard’s view is.

2. Connected servers panel — Lists all servers the bot is connected to and the sync/health state for each server.

3. Per-server diagnostic — If any server “needs attention” the Status page highlights it with an explanation (for example, missing bot invite permissions, out-of-date webhook, or other issues).

4. Action items — Use the page to identify follow-up actions: send or re-send an invite with full permissions, re-sync a server, or review recent actions for failures.

Tips

• Check Last sync before troubleshooting — if it’s old, re-sync first.

• When a server needs attention, click into the connected server entry for more context (the UI will show buttons or labels like “Selected / Complete / Synced”).

2) Branding — control how the bot presents itself in Discord

What it is

• The Branding page lets you update the bot’s Discord presentation: avatar/banner, bot name, the short bot description, and presence (status emoji, presence text, and presence state). It’s the place to make the bot feel like a native, polished part of your server.

Where to look

• Open Dashboard → Branding.

How to use it

1. Profile identity area — Upload or change the bot banner and avatar. The dashboard shows a preview of the banner behind the bot avatar.

   • Allowed formats are typically JPEG/PNG/GIF for banner/avatar (UI may indicate allowed formats).

2. Connected server block — Confirms which server you’re editing branding for.

3. Bot name and description — Edit the bot name (note: Discord username changes may be rate limited) and add a short description that appears in the server.

4. Presence controls — Set:

   • Status emoji (the small emoji that appears beside the bot),

   • Status text (“Watching launch traffic” style example),

   • Presence status (Online / Idle / Do Not Disturb / Invisible).

5. Save/Publish — Use the on-screen save/update control to apply branding changes. Some fields (like the bot name) may be rate-limited by Discord — the UI will warn you if that’s the case.

Tips

• Keep the description concise and focus on what the bot does for that server.

• Use the preview to check how avatar & banner look together — banners appear behind the avatar in preview.

3) Dashboard Permissions — who can use the web console

What it is

• Dashboard Permissions controls which people can access and manage the Rocket dashboard (the website). This is different from Discord command-level permissions — Dashboard Permissions is about web access and management rights for collaborators.

Where to look

• Open Dashboard → Dashboard Permissions.

How to use it

1. Invite or add collaborators — Add other staff or managers by entering their Discord ID or email, depending on the UI field. These users will be able to open the Rocket dashboard for your server.

2. Assign roles — The dashboard supports roles like Manager or Custom role assignments (the UI labels and descriptions explain what each role can do).

3. Review counts — The page summarizes how many Authorized Members, Managers, and Custom Entries exist — use this summary to audit access.

4. Manual overrides & audit — Some changes show up as manual overrides; use the audit/audit-log page (or recent actions) to review permission changes.

Guidance

• Grant dashboard access only to trusted server staff — dashboard access typically allows configuring automations, integrations, and deeper settings.

• Regularly review Authorized Members and Managers to remove stale access.

4) Command Permissions — control who can run Discord slash/prefix commands

What it is

• Command Permissions manages which Discord members can run GR Rocket commands in your server. This is Discord-specific: it controls slash command and prefix command execution rights (managers, custom roles, default permissions, and manual overrides).

Where to look

• Open Dashboard → Command Permissions.

How to use it

1. Top summary — See quick counts: Authorized Members, Managers, Custom Entries, Manual Overrides.

2. Add by Discord ID — Add a Discord user ID (you can copy IDs from Discord via Shift+Right-Click on a user) into the ID field to authorize them.

3. Assign a role:

   • Manager — managers can run virtually every Rocket slash command (except billing), and usually have broad access.

   • Custom — gives you granular control: pick which command categories or specific command operations they may run.

4. Core Command Operations — Use the toggles for core operations like “Ticketing, Verification & Queue Actions” or “Guild Sync Commands” to allow staged or sync commands.

5. Automation & Messaging — The page lists groups of command families (Custom Command Manager, Social Alert Commands, etc.) and checkboxes to grant access to those modules.

How to think about roles

• Use Managers for trusted server administrators.

• Use Custom for moderators or roles that need specific command families (for example, staff-only serverstats or moderation actions).

• Keep billing and sensitive commands limited to the smallest team necessary.

Tips

• Members with Discord Administrator or Manage Server permissions are often auto-added as Managers — check the UI note about auto-adds.

• If a command doesn’t behave as expected in Discord, confirm Command Permissions before debugging bot code.

5) Command List — browse, filter, and copy usage

What it is

• The Command List is the catalog of all GR Rocket commands (slash and legacy prefix), with descriptions, examples, tags, and subcommands. Use it to discover commands available to your server and learn the correct syntax and options.

Where to look

• Open Dashboard → Command List.

How to use it

1. Summary metrics — Top-of-page cards show counts (Total Commands, Slash Commands, Prefix Commands).

2. Search bar — Search commands, subcommands or keywords. Useful for quickly locating a command like /serverstats or /moderation ban.

3. Filters — Filter by:

   • All Categories or a specific category (Moderation, Community, Automations, etc.)

   • All Commands, Slash Only, or Prefix Only.

4. Command details — Click a command entry to view:

   • full description,

   • tags (who can use it),

   • examples,

   • options and subcommands (with option types and placeholders),

   • any notes (aliases, rate limits, etc.).

5. Copy usage — Many commands include a “Copy usage” quick button so you can paste the exact example into Discord or your documentation.

Example: /serverstats

• The Command List entry provides the /serverstats base command plus subcommands like collect, preview, export, and settings and lists options for each (scope, include, channel). This is the best place to learn what options exist and to copy an example for immediate use.

Putting it all together — workflow suggestions

• Daily check: Open Status first thing to verify sync and health for your servers.

• Brand updates: Use Branding when you’re launching a new server theme, seasonal event, or simply to keep the bot’s look consistent with your community branding.

• Onboard staff: Use Dashboard Permissions to invite peers to the dashboard and then use Command Permissions to give them the exact command access they need (Managers for full control, or Custom for specific modules).

• Training and docs: Point new moderators to Command List for examples and to copy usage snippets — this reduces mistakes and accidental misuse.

• Audit periodically: Review both Dashboard Permissions and Command Permissions for stale or overly-broad access; use the dashboard audit log to track changes.

Quick troubleshooting checklist

• Bot appears offline or Pending invite / permissions on Status:

  • Verify the bot is in the server with the correct permissions.

  • Re-invite the bot with required scopes and permissions, then re-sync.

• Command not available or permission denied:

  • Confirm the command exists in Command List and check defaultPermission or required roles.

  • Check Command Permissions for manual overrides or custom role assignments.

• Branding changes not applied:

  • Remember Discord may rate-limit name changes. Use the Branding preview and check the last update/time.