Skip to main content
Discord is the everyday surface for members and many staff workflows. The dashboard remains the control plane for configuration, approvals, audit, and repair.

​
Required bot configuration

Enable these privileged intents in the Discord Developer Portal:
  • Server Members Intent for live member, role, and guild-membership checks.
  • Message Content Intent when using ticket conversation capture and history recovery.
Rodyne also uses Guilds and Guild Messages. Grant only where needed:
  • View Channels
  • Send Messages
  • Embed Links
  • Attach Files
  • Read Message History
  • Manage Channels
  • Manage Roles
  • The relevant native moderation permissions if ban, kick, or timeout workflows are enabled
Discord Administrator is not a Rodyne staff grant. Dashboard access comes from workspace membership or an enabled, verified Discord role policy.

​
Role hierarchy

Move the Rodyne bot role above:
  • Mapped member roles it must add or remove.
  • Support roles it must add to private ticket channels.
  • Members it must moderate.
Rodyne checks the actor and bot’s current Discord permissions and hierarchy at execution time. A previously valid request can safely fail if roles changed while it waited.

​
Connect and scan

1

Bind the guild

During activation, choose the managed guild and use the generated bot invitation. The selected server is locked into that setup attempt.
2

Run the permission scan

Open Bot Management → Integrations → Discord and refresh the role/permission catalog. Resolve missing or blocked capabilities.
3

Review managed roles

Use the scanned catalog when creating mappings, staff role rules, and ticket types. Refresh again after significant Discord role changes.
4

Verify registration

Open Bot Management → Commands and Activity. Built-in and enabled custom commands reconcile to the guild automatically.

​
Command troubleshooting

​
Verify with a test account

Use a separate non-staff Discord account to confirm:
  1. Public help and verification commands are available.
  2. Verification opens the expected Cnect flow.
  3. Only eligible mapped roles are changed.
  4. A ticket channel is private from unrelated members.
  5. Closing and reopening enforce the expected send/access behavior.

​
Guided walkthrough

Discord capability card in Rodyne Integrations

Discord capability health is visible before commands, panels, or role automation go live.

The screenshot above is from the live Rodyne product. Use it to orient yourself, but rely on the current record state and live provider checks when operating the workspace.

​
Operating procedure

1

Verify the guild

Match the connected guild ID with the server where the bot was invited.
2

Enable intents

Enable Server Members and, when ticket capture is used, Message Content in the bot application.
3

Place the bot role

Move it above every managed role and member it must moderate.
4

Refresh capability data

Run the Rodyne scan after changing Discord permissions or hierarchy.
5

Exercise real paths

Test a command, a private ticket, and role reconciliation from separate member accounts.

​
Acceptance checks

​
Failure recovery

Discord permission failures are evaluated at execution time. Capture the channel, target role, actor, and bot hierarchy as they exist when the operation fails; an earlier successful scan is not proof that the live state is still valid.

​
Continue the workflow

Configure commands

Build ticket panels