Configure the pieces your community actually uses.

Recommended setup

1. Create one or more ticket categories and configure intake questions.
2. Choose a Discord category for each ticket category, set per-user limits, then add staff roles with View, Action, or Ping access.
3. Optionally set first-response and inactivity SLA targets. Modra reminds the category ping roles in the ticket when a target is missed.
4. Create one or more launchers, choose which categories each contains, customize the embed, and publish it to the desired channel.

Workflow notes

• Different categories may share a launcher while routing tickets to separate Discord categories.
• Dashboard page permission and category roles are both required unless the access group has an explicit View All or Action All permission.
• SLA reminders send once per inactive period and become eligible again after new activity.
• Staff can claim, close, add access, escalate to a role, redirect tickets to another configured category, and schedule auto-close from Discord.
• Open tickets are the default dashboard view; archived records retain transcripts and action history.

Recommended setup

1. Create categories, questions, applicant requirements, viewer/ping/action roles, and acceptance roles. Written questions can optionally require a minimum word count.
2. Set a pending review channel, optional completed log channel, internal thread behavior, and applicant discussion category.
3. Optionally set first-review and inactivity SLA targets. Modra reminds the category ping roles in the review channel when a target is missed.
4. Create launchers and publish each to the appropriate Discord channel.

Workflow notes

• Applicants can choose a guided DM interview or secure web form; the web link is offered when DMs are unavailable.
• Minimum word counts are supported for short and paragraph answers and are enforced in both the DM interview and secure web form.
• Unviewed applications show a New marker and dashboard navigation badge for each reviewer independently.
• Dashboard page permission and category roles are both required unless the access group has an explicit View All or Action All permission.
• Long submissions post a summary plus a secure dashboard link instead of overflowing Discord.
• Accepting or denying from either Discord or the dashboard keeps the pending message and record synchronized.

Recommended setup

1. Enable Appeals and create one or more categories with questions.
2. Set category viewer and action roles, repeat limits, cooldowns, and the staff response name.
3. Optionally configure a confirmed approval action: unban, add a role, or remove a role.
4. For a dedicated address, create a CNAME such as appeals.example.com pointing to modra.kenzie.wtf, save it in Appeals setup, then verify DNS.

Workflow notes

• Banned and former members can sign in with Discord and submit without joining the server.
• Follow-up questions and final decisions are sent by private DM and recorded in the dashboard. Direct DM replies are attached automatically when one appeal is waiting; the Reply to appeal button handles multiple concurrent appeals safely.
• Discord actions never bypass permissions or role hierarchy. A decision remains recorded if Discord rejects its optional action, and the dashboard displays the warning.
• View, Review, View All, and Action All permissions work with per-category Discord roles just like Tickets and Applications.

Recommended setup

1. Select the verification channel and verified/unverified roles.
2. Customize the rules message and button, then set the minimum account age if needed.
3. Configure the visitor pass role, duration, launcher, and permanent application relationship when temporary access is offered.

Workflow notes

• Modra must sit above every role it assigns or removes.
• A pass defaults to 72 hours, can only be claimed once, and is not removed at expiration when an accepted permanent application protects the same access.
• Members without a pending or accepted application receive an expiration DM.

Recommended setup

1. Choose separate join and leave channels.
2. Select a dynamic card or embed, customize copy and colors, and verify the live preview.
3. Add optional starter roles and decide whether to send a welcome DM.

Workflow notes

• Use {server}, {member}, {username}, and {memberCount} where the field supports placeholders.
• Keep join messages public and leave messages staff-only by selecting different channels.
• Starter roles still require correct Discord role hierarchy.

Recommended setup

1. Create a role menu and choose its Discord channel.
2. Add the roles members may select and configure the menu copy and style.
3. Preview, publish, and test using a regular member account.

Workflow notes

• Modra cannot assign managed roles or roles placed above its own Discord role.
• Re-publish after materially changing a live menu.

Recommended setup

1. Configure application/review channels, streamer and Live Now roles, notification channels, and opt-in ping behavior.
2. Set required games and title keywords. Add already-approved streamers directly when migrating an existing program.
3. Have approved streamers run /streamer connect, then use the test notification before relying on a live broadcast.

Workflow notes

• A real alert appears only while the current platform game and title pass every configured requirement.
• One alert combines available platform links, refreshes live data and imagery, and is deleted when the broadcast ends.
• Removing the streamer role removes active promotion while retained profile data follows the configured retention policy.

Recommended setup

1. Create an announcement and choose its destination channel.
2. Add optional role pings, image, thumbnail, fields, footer, and community-themed accent.
3. Save as a draft, schedule it, publish immediately, or mark it as a reusable FAQ.

Workflow notes

• FAQ reposts use /faq and intentionally do not repeat announcement pings.
• Published one-time records can be deleted from dashboard history without deleting the Discord message.

Recommended setup

1. Create a sticky from the dashboard or use /sticky set in Discord.
2. Select the channel and customize the title, content, image, footer, and accent.
3. Send a normal message to verify Modra replaces the old sticky at the bottom.

Workflow notes

• Only one Modra sticky should be configured per channel.
• Use /sticky remove or the dashboard to stop and remove it.

Recommended setup

1. Choose the command prefix, which defaults to !.
2. Create a unique trigger such as howtoconnect, then add the response embed, image, GIF, and allowed roles/channels.
3. Use the Discord preview, save, and test the full command such as !howtoconnect.

Workflow notes

• Use FAQ responses when the content already exists as an announcement.
• Only allow broad member access when the response is safe to use repeatedly.

Recommended setup

1. Set the overall giveaway manager roles.
2. Create the prize, description, channel, end time, winner count, eligibility rules, and accent.
3. Preview and publish, then monitor entries from Discord or the dashboard.

Workflow notes

• Manager roles apply across giveaways for that community.
• End chooses winners, Cancel chooses none, and Reroll draws replacements after completion.

Recommended setup

1. Choose the suggestion channel and optional staff review channel.
2. Configure reviewer roles, cooldown, minimum account age, submitter visibility, and downvotes.
3. Submit a test with /suggest and confirm voting and review controls.

Workflow notes

• Anonymous display hides the submitter publicly, not from authorized staff records.

Recommended setup

1. Add manager/ignored roles, protected channels, alert channel, and cleanup channels.
2. Configure burst thresholds, account age, invites/domains, response action, timeout, and lookback.
3. Add Advanced AutoMod rules for banned phrases, duplicate text, mass mentions, excessive caps, emoji spam, or oversized messages. Choose each rule’s response and optionally narrow it to specific protected channels or member roles.
4. Enable automatic enforcement only after reviewing the settings. Configure honeypot channels and publish the warning card.

Workflow notes

• New Advanced AutoMod rules default to Delete message. Warn, timeout, kick, and ban must be deliberately selected.
• If several rules match one message, Modra applies the strongest configured response once and records every matched rule.
• Advanced rules run only in protected channels while automatic enforcement is enabled. Global and rule-specific ignored roles bypass matching.
• Modra ignores its own honeypot warning posts.
• Use /purge with an explicit confirmation; messages older than Discord’s bulk-delete window are handled individually.
• Test enforcement with a disposable account and confirm deletion, member action, staff alert, and audit entry.

Recommended setup

1. Choose moderator roles and whether affected users receive DMs.
2. Set case retention, then test a non-destructive warning or note.
3. Use the dashboard history or /mod history to review a member.

Workflow notes

• Community-triggered DMs name the Discord server they came from.
• Discord role hierarchy and native Discord permission rules still apply.

Recommended setup

1. Add the FiveM endpoint, status channel, connection URL/command, and display copy.
2. Set refresh interval, offline failure threshold, timezone, and restart times.
3. Preview, publish, and compare the live population and connection data.

Workflow notes

• Restart times use the timezone selected in the dashboard.
• Maintenance mode can replace normal status messaging without removing the configured endpoint.

Recommended setup

1. Set retention and grant dashboard view access only to trusted roles.
2. Filter by action, actor, target member, or time while investigating.

Workflow notes

• Audit records show usernames where available and preserve Discord IDs as supporting identifiers.
• Anonymous ticket replies still record the actual staff actor internally.