Modra

QUICK START

Set up Modra without the guesswork.

Keep this guide open beside your private setup link. Most communities can finish the essentials in one pass.

Before you begin

Use the assigned owner account, make sure you can manage the Discord server, and have your preferred channels, staff roles, logo, avatar, and banner ready.

  1. 1

    Open your private setup link

    Use the link provided by Modra or your partner contact. Sign in with the Discord account assigned as the community owner. The link is private and intended for that owner.

  2. 2

    Install Modra in Discord

    Select Open Discord, choose the intended server, and approve the requested permissions. You must own the server for it to appear during guided installation.

  3. 3

    Confirm the connection

    Return to the setup page, refresh the server list, select the connected server, and continue. If the server is missing, confirm the bot appears in its member list.

  4. 4

    Configure or skip tickets

    Choose where tickets are created, add staff roles by searching for them, decide which roles are pinged, and add intake questions. You can skip tickets entirely and enable them later.

  5. 5

    Choose your modules

    Enable only the tools your community will use. Dependencies are enabled automatically, and disabled modules remain hidden from normal dashboard navigation.

  6. 6

    Apply community branding

    Select primary and secondary colors, add your community logo, and customize the bot profile. Use Adjust crop and position to drag and zoom the avatar or banner before saving.

  7. 7

    Review and launch

    Confirm the summary and complete setup. You can return to Modules, Branding, Dashboard access, or the Setup guide whenever changes are needed.

Prepare Discord first

  • Create the categories and channels you want Modra to use, including staff-only review and leave-log destinations.
  • Create staff, verified, notification, streamer, Live Now, and acceptance roles that your enabled modules will use.
  • Place Modra's role above every role it needs to assign, restore, remove, or take moderation action against.
  • Give Modra channel-specific access to every category and channel used by an enabled module.
Discord role hierarchy still applies

Modra can only assign or remove roles positioned below its highest bot role. It can only timeout, kick, or ban members whose highest role is below Modra's highest role, and it cannot moderate the Discord server owner. Administrator permission does not override these hierarchy limits.

Channel access: scoped permissions are recommended

Modra must be able to view and use every category or channel configured in the dashboard. Permissions inherited from a category are sufficient unless a channel-level override blocks the bot. Owners may optionally grant Modra's bot role Administrator for blanket access, but this gives the bot broad control across the entire server. Enable it only if you understand and accept that security risk; least-privilege channel permissions are the recommended setup.

Recommended image sizes

Bot avatar

512 × 512 px, square. Keep faces and logos centered inside the circular safe area.

Bot banner

600 × 240 px (5:2). Keep important content away from the lower-left avatar overlap.

Use Upload image beside an image field to store it in the community media library, or choose Choose saved to reuse an existing asset. Direct HTTPS URLs remain available when an image is already hosted elsewhere.

Connect a vanity dashboard address

Community owners and staff with branding access can give staff a familiar address such as modra.yourcommunity.com. Open Branding, save the full hostname, and add the CNAME record shown by Modra at your DNS provider. Return to Modra and select Verify DNS after the record has propagated.

  • Use a subdomain, not the community's main website address.
  • Leave a Cloudflare record set to DNS only until Modra verifies it.
  • The first HTTPS visit can take a few seconds while the certificate is prepared.
  • The vanity address redirects to the community dashboard on Modra's primary domain.

Run these first checks

  • Run /modra status and confirm the correct server name.
  • Test each enabled launcher, role menu, and verification button.
  • Use a second non-staff account before relying on permission boundaries.
  • Confirm Modra’s role sits above every role it needs to assign, remove, or moderate.
  • Confirm staff-only destinations are not visible to a regular member account.
  • Keep destructive purge, honeypot, and ban testing in disposable channels and accounts.
Open dashboardRead full documentation