Rova documentation

Documentation

Pick a feature, get it set up, and find the commands you need.

The basics

Getting started

You need Manage Server or Administrator, or be the server owner, to request Alpha access and install Rova. Using the dashboard requires Administrator in the selected server.

Open Add Rova (Alpha) and select Request Access. Allow access to your Discord profile and server list so Rova can show the servers you manage.
Choose your server and select Request Alpha access. Life reviews the request. Return to the install page and use Refresh status to check whether it is pending, approved or not approved.
Once approved, select Add to Discord. Rova supplies the permissions needed for her features. Check the selected server and permissions on Discord’s authorization screen, then authorize the installation. Servers already approved can go straight to this step.
Open the dashboard and sign in with Discord.
Choose your server from the server selector. Check the selection before changing settings.
Choose a Rova updates channel and select Save and finish setup. This required channel receives maintenance notices with an estimated return time. A staff channel works; allow Rova to view it, send messages and embed links. The setup prompt then disappears. To change the channel later, open System → Rova updates.
Pick a feature from the sidebar. Create the channels and roles it needs in Discord, then select them in the dashboard.
Save the section, review its preview, and use its publishing or setup action when you’re ready.

Settings belong to the selected server. A staff role that can manage tickets or partnerships in Discord does not, by itself, grant dashboard access.

If your updates channel is deleted or Rova loses access, the required setup prompt returns when the dashboard checks it. Choose a replacement or restore permissions, then use Refresh status. Maintenance notices do not ping members, and saving the channel does not send a test message.

Dashboard Overview shows what’s set up and what needs attention. Switching servers keeps their settings and records separate. The dashboard accent is saved for the selected server and shared by everyone who opens its dashboard.

New servers start fresh. Choose your welcome and booster channels, staff roles, and moderation settings; Rova won’t copy another community’s setup. An approved server that leaves and rejoins keeps its saved settings.

Alpha availability: installation is currently limited to approved Alpha servers. AI features are coming soon for Alpha servers. They are currently used in Ronova Mains and during development testing. The guides explain which features need AI.

Read the Privacy Policy and Terms before installation. For Alpha access, a feature request, or a data request, see Support.

Give Rova the right access

Check Rova’s role permissions and the channel’s overrides. She needs access to each channel where you want a feature to work.

Your Administrator permission is for dashboard access; Rova does not need Administrator. Give the bot the individual permissions required by the features you enable. Discord’s command permissions can further limit who sees or uses a command.

The installation page requests the permissions used by Rova’s supported features, without Administrator. For the Alpha, sign in and choose a server you manage; you do not need to look up its ID. Discord shows the permission list before you authorize installation. Granting permissions does not automatically configure features or publish anything; channel restrictions and role hierarchy still apply.

Messages and previews: Allow View Channel, Send Messages, and Embed Links where Rova posts. Features that read existing messages also need Read Message History; file delivery needs Attach Files.
Role rewards and assignments: Reaction roles, role categories, partner assignments and rewards need Manage Roles. Place Rova’s highest role above every role it should assign or remove. Managed integration roles cannot be assigned this way.
Private tickets: Installation includes Manage Channels to create tickets, Manage Roles to set channel access, and Pin Messages for ticket controls, plus the supported message and preview permissions. Check the selected support roles before opening tickets for members.
Webhook publishing: Allow Manage Webhooks in the destination. For a picker that asks for an existing webhook, create one in Discord under Channel Settings → Integrations → Webhooks, then refresh the picker.
Reaction panels: Also allow Add Reactions and Manage Messages in the panel channel. Target roles must be safe for members to assign to themselves.
Moderation: Grant Moderate Members, Kick Members, Ban Members, or Manage Messages only for the actions you use. The staff member invoking an action needs its permission too. Rova cannot act above its role position or against the server owner.
Nickname protection: Allow View Audit Log and Manage Nicknames, with Rova above the protected members. Notification channels also need message access.
Winner threads and timed rewards: Public or private winner threads need their corresponding Create Public Threads or Create Private Threads permission, plus Manage Threads and Send Messages in Threads. Timed role rewards also need View Audit Log to verify ownership before expiry, along with the role permissions above.

If a channel or role is missing from a picker, check its permissions and role position first. Refresh the dashboard after changing Discord settings.

Saving, publishing, and drafts

The save bar applies to the section or editor you’re working in. Discard returns that draft to its saved values; it asks for confirmation when there are changes.

Moving between dashboard sections keeps their drafts. Save before refreshing, closing the page, signing out, or switching servers.
If a save fails, your draft stays in place. Correct the highlighted fields or retry after fixing the reported problem.
If another administrator has saved newer settings, review the differences before saving your own changes.
A preview shows how a message will look. Its buttons do not perform Discord actions.

Save and Publish are separate actions when the editor provides both. Save first, then publish. Saving changes to an already active panel can update its existing Discord message. Saving an enabled schedule or automation can also affect what runs next; read the action’s description.

Dates generally use your local timezone. A feature with its own schedule timezone, such as Starboard, labels that setting separately.

Bot appearance

Open Home → Bot Appearance to edit the bot’s profile for the selected server. Review the available nickname, bio, profile picture, and banner fields; crop an uploaded image in the editor and check its preview before saving.

These changes affect Rova’s profile in this server. If a field is unavailable, its explanation tells you why. Discord can limit how often a profile changes; if that happens, keep your draft and wait for the retry time shown.

Bring communities together

Partnerships

Publish an incoming partner ad, place the server in your Partner List, record its representatives, and give them your Partner role in one Discord workflow. Once an administrator has set it up, your configured Partner managers can handle each partnership without returning to the dashboard.

Review and publish a partnership

Run /partner post source: with the incoming ad’s Discohook share or data link, or a supported TinyURL. Rova shows the ad and a Pending Confirmation preview in the channel where you ran the command.
Choose a destination if more than one is configured. Check the server name and invite; use Edit Server Details to correct them, or Enter Server Details if they could not be detected.
Open Optional: list placement, representatives & role and select the partner server. Choose its Partner List section and column, select its representatives, and choose whether to Grant Partner role to these representatives. These choices are optional and are reviewed before publishing.
Select Publish Ad. Rova sends the announcement and ad, applies the selected list placement, updates the representatives in its internal tracker, and grants the selected Partner role. An already-published, configured Partner List is updated automatically.

Nothing changes until you publish. Representatives can be tracked without adding the server to the public list. Clearing representatives removes their tracker assignments; it does not remove roles. If your Partner List has not been published, its selected placement is saved for you to publish from the dashboard.

Set it up once

In Partner Ads, add a named destination with its channel and incoming webhook, then customize the announcement. Choose your Partner manager roles and optional Partner role, then save. Complete the one-time Discord authorization so Rova can make /partner available to those managers. Until that finishes, the commands are available to administrators by default. Rova needs permission to create the ad preview and grant any selected role.
In Partner List, create your sections and categories, or import an existing list using the steps below. Choose Rova's built-in layout or keep your own design. Select its publishing channel and webhook, save, and choose Publish so later partnerships can update the directory automatically.
Optionally, in Partner Assignments, choose a panel channel, save, and select Publish or refresh panel to display the tracked representatives in Discord. The internal tracker works without a published panel.

To share your own server’s ad, save it in Partner Ads and use /partner ad for its share link. For later adjustments, /partner assign, /partner unassign, /partner list, and /partner role are also available; they are not separate steps required for each incoming ad.

Import an existing Partner List

Already have a list made with Naya, another bot or Discohook? Choose Rova's design to import its partners and categories into Rova's layout, or My own design to keep its headings, artwork, colors and layout as well.

Paste the source under Bring your existing list and select Import list. For several Discord messages, paste one message link per line, in display order, up to 20 links. Discohook share links, exported JSON and JSON files also work.
Rova finds the partner names, invites and categories and prepares the draft in your chosen design. If it replaces an existing draft, review the counts and confirm. Matching partners keep their representative assignments.
Review the categories, links and preview. With My own design, supported lists are connected automatically and text outside partner areas stays unchanged. With Rova's design, your Rova colors and images stay in place.
Select Save, then Publish. Future partner changes update the connected areas.

Unusual layouts may need a little help. Rova explains anything it cannot import automatically. For custom designs, open Advanced: adjust category connections to connect partner lines to categories yourself. Importing alone never changes your published list.

Working with a long list? Expand only the sections and categories you need. Each category shows its partner count, and search finds names, invites and categories. Open Edit section details or Edit category details to change labels and appearance. These editor controls do not change how the list looks in Discord.

For Discord imports, Rova must be installed in the selected server with View Channel and Read Message History access to the source. The original messages stay untouched; Publish uses your configured Rova list destination. Another bot's buttons, hidden pages, uploaded files and internal settings do not transfer. Replace expiring attachment image links with permanent HTTPS image links before publishing.

Custom designs keep their original message boundaries. If the filled list is too large for Discord, Rova points out the problem before saving. Split the design in Discohook and import it again, or switch to Rova's built-in layout for automatic page sizing. Switching layouts keeps your partners and imported design.

Partner Assignments can show partners without representatives and retained partners no longer on the public list. Review the effect of removal before confirming: a directory entry, a representative assignment, and a Discord role are separate records. Invite-health notices flag an invalid invite for review; they do not silently replace the saved invite.

Mentioning Rova with “give me the partner ad” or “post this partner ad” requires natural-language access, which is coming soon for Alpha servers. /partner ad and /partner post remain available without AI. Posting still requires the same permissions and confirmation.

Give people something to join

Events & submissions

Open Community → Events and choose New event.
In Setup, enter the title, submission channel, start and end times. Choose a private staff review channel and Event Staff roles if you want to review entries in Discord. Add participation rewards if you want to award roles.
In Submission days, set each day’s opening time, prompt, and form. A day closes when the next begins; the final day closes at event end.
Choose whether to Post submissions to Discord. Leave it off to keep saved responses and uploads in the dashboard. If enabled, review the destination and posting schedule.
Review Messages, then save. Members use /submit in the submission channel during an open day.

Staff review posts arrive immediately with submitted answers and files. Event Staff and administrators can Accept an entry or Reject it with a reason sent privately to the member. Auto-accept hides Accept and keeps Reject available.

With staff review enabled, open Messages to customize the rejection DM. Use your moderation branding or design a custom embed with its own text, color and artwork. You can paste JSON or import a .json file, including a single-message Discohook export, and preview the result. Use {user}, {event}, {day} and {reason} to personalize it. Imports without a reason placeholder get a Reason field automatically.

Rejection lets the member submit a replacement while that day is open. Blocked DMs do not undo the decision, and the delivery status remains visible to staff.

Each day can have its own questions, choices, and uploads. Choose private staff channels for review and check the audience before enabling a public relay. Only accepted entries enter scheduled relays. Previously published entries stay until deleted from the dashboard.

Rewards count accepted submission days. Multiple accepted entries on the same day count once. Without manual review, entries are accepted immediately. Rejection or changes to a reward rule do not remove roles already awarded.

Automatic announcements can determine when a day opens. Review the daily posting order in the editor before enabling them. Archive closes the event to further submissions and retains its saved entries.

Make room for a private conversation

Tickets & moderation

Start with a member, not a command list

Run /user user: to bring a member’s moderation history, staff notes, roles, activity, and ticket summary into one overview. You need Moderate Members permission or Administrator access.

Use a staff-only channel. The overview and its notes and history replies are visible in the channel where you run the command; they are not private replies to you.

Choose Notes to read the member’s notes, then Add Note to record context. Review and confirm the note before it is saved. The overview and Notes list update in place when you add, edit or delete a note. Confirmations use the same Notes message, and clicking Notes again reopens that list without posting another one. Only its original author or an Administrator can edit it. Administrators can also choose Delete beside a note, then confirm its removal.
Choose Open ticket to start a Staff Inquiry for that member. Enter the reason and context in the form. The member must still be in the server, and you must have the configured ticket-staff access.
Use Warn, Timeout, Kick, or Ban when appropriate. Available buttons follow your permissions; stronger actions require the corresponding Discord permission. Enter the reason and any duration, then review the confirmation. Role hierarchy still applies.

The overview includes recent history and ticket links. Full History appears when more history exists than the overview can display.

Set up the ticket workflow

In Ticket Defaults, select an open category, transcript channel, and global support roles. Save.
In Ticket Types, configure the types members can open. A type can override its category, transcript channel, and support roles.
Customize Panel Message, or keep its generated layout. Save the section.
Open Publish Panel, choose a channel, and select Publish or update.

/ticket is available to Administrators and configured ticket staff. Members use the published ticket panel. Connect Discord when prompted in Ticket Defaults so Rova can show the commands to your staff roles automatically.

Open a staff inquiry

Authorized staff can use /ticket open subject: user: to open a private ticket for a member. This defaults to Staff Inquiry. Add optional details or choose another configured type.

Use the ticket’s Claim, Add User, Edit Ticket, and Close controls as needed. A closed ticket offers Transcript; generating one archives it to the configured transcript channel. Closing and deleting are different actions.

Limit new self-service tickets

Under Ticket Defaults → Ticket blacklist, find a member by name or Discord user ID, select them, and save Ticket Defaults. Use Unblock and save to reverse the restriction.

Administrators can also use /ticketblacklist add user:, /ticketblacklist remove user:, and /ticketblacklist list. Existing tickets remain available; authorized staff can still open a ticket for a blocked member.

Where natural-language moderation is available, an Administrator can mention Rova with “blacklist @member from creating tickets” or ask to remove that restriction. Servers without AI should use the dashboard or slash commands.

Keep transcript links within the intended audience: someone with a hosted transcript link may be able to read that transcript. Never post staff notes or private ticket links in a public channel.

Safety settings & media review

Manual moderation commands work independently of AI. Use /user for a member overview, or the direct warn, timeout, kick, ban, notes, and purge commands in the command reference. Actions still check staff permissions, protected members, and role hierarchy.

Make moderation notices yours

Open Moderation → Safety Settings → Moderation branding to choose your notice name, embed color, image and server invite. Upload a PNG, JPEG or GIF, or use an HTTPS image link. Check the preview and save. These settings also work without AI.

By default, notices use your server’s name, with no banner or invite. Your saved branding appears in moderation confirmations and member notices. The Blacklist section shows your Discord AutoMod keyword rules and can be refreshed without changing them.

Account-age protection

In Moderation → Safety Settings, set a minimum account age and any exempt user IDs, then enable and save the rule. It checks future joins only and can kick accounts younger than the limit; bots and exempt members are skipped. Rova needs Kick Members. Existing members are never swept by enabling this setting.

The server owner controls the protected-user list and the authorized mass-ban list. A listed mass-ban user must also have Administrator permission. Being a dashboard administrator alone does not grant this authorization.

AI monitoring and media lists

On an eligible server, choose the monitoring scope, a private staff alert channel, and any staff pings. A new server is not monitored until its moderation configuration is saved. Review the scope before the first save: an empty monitored-channel list means all accessible channels, not none. Run safe test evaluates sample text without deleting messages or producing an enforcement alert. Review real alerts before using Seen, User Info, False Alarm, or removal actions.

Approved Media contains saved false alarms. Unapproved Media contains blocked images, GIFs, videos, and links. Remove + blacklist adds media from a Discord review; the action is absent on text-only content. Removing a saved rule changes future checks, not past messages.

Without AI moderation: AI monitoring, automatic media-blacklist enforcement, moderation alerts and staff pings, and AI review actions are unavailable. Saved rules remain visible where supported. Configured text-keyword rules can still delete matching messages, but their moderation alerts and pings pause too. Manual moderation and account-age protection, including its separate safety alerts, remain available. A visible media list does not mean messages are currently being checked.

YouTube & Reddit feeds

Open Feeds & Relays → Subscriptions. Add a YouTube channel ID or handle, or a subreddit name or URL.
Choose the Discord destination. Review the source and whether Reddit posts with the Leaks flair should be included, then save.
Use Preview a source to inspect a recent item without posting it. Check delivery status and any pending review items.

/youtuberss and /redditrss provide subscription, listing, removal, and preview commands for staff with Manage Server. Unsubscribing stops future delivery; it does not delete posts already sent to Discord.

YouTube and Reddit feeds work without AI. When AI moderation is off or unavailable to your server, new items publish without an AI review. When you enable AI moderation, items are reviewed before publication; a failed or unavailable reviewer does not silently bypass review. Existing flagged items remain held for a staff decision. Subscription settings and non-AI filters still apply.

Reaction roles

Members choose roles by reacting with emoji. Configure panels in Roles & Automation → Reaction Roles.

Create a panel. Choose Create a new message or Use an existing message, then select its channel.
For a new post, compose or import its design and select a webhook. For an existing post, select the message or provide its link or ID.
Add an emoji and assignable role for each choice. Choose the reaction mode and any eligibility restrictions.
Save the panel, then choose Publish message or Attach reactions.
Test with a regular member account to confirm both permissions and the intended role behavior.

Roles with Administrator or sensitive server/channel permissions stay selectable when Rova can manage them. Persistent Permission warning messages identify the role, permissions and channel. Warnings do not block saving or assignments. Review those permissions before publishing; Administrator can give members full server access. Missing roles, everyone, managed roles and roles at or above Rova remain unavailable.

Normal adds a role on reaction and removes it on unreact. Unique allows one choice on the panel. Binding makes a one-time choice. Other modes include Verify, Drop, Reversed, Lock, and Temporary; read the selected mode’s description and any duration before publishing, especially for modes that remove roles.

Use Repair reactions when a tracked message’s reactions are missing. Pause assignments stops reaction handling. Removing a panel stops tracking it; it does not delete the Discord message.

Role member-count milestones

Open Roles & Automation → Role Milestones, select an audit channel, and add a milestone. Choose the source role to count, the member threshold, and the role to award. Rova needs Manage Roles and must be above the award role.

Each enabled milestone runs once, using the members holding the source role when its threshold is reached. This is not a continuously refreshed membership rule. Review the saved execution status and any assignment failures in the audit channel before using a retry or abandonment action. Removing a milestone does not undo awards already made.

Giveaways

Open Community → Giveaways and choose New giveaway.
Set the title, prizes, destination, number of winners, and schedule. Review entry requirements and any winner rewards.
Check both previews: Giveaway post and After the draw.
Choose Save template to keep the setup. Then choose Publish giveaway, or Schedule giveaway when linked to a future Event.

Members enter through the Discord giveaway post. The dashboard tracks entrants, results, and draw activity. End now closes entries and starts the draw; Cancel ends the giveaway without choosing winners.

Entry rules can require roles, account age, time in the server, activity, or membership in listed servers. Bonus roles can add chances or use only the highest matching bonus. Members may need a separate Discord sign-in to verify entry requirements; this does not grant dashboard access.

Optional winner actions include a role and a thread for each winner. Check thread visibility and the opening message before enabling them. A timed winner role is not removed if the winner already held it. Templates and recurring schedules are separate from an individual published draw.

If winners were saved but the Discord announcement failed, use Publish saved result. Reroll new winners selects different winners; it is not a way to retry the same announcement.

Check any eligibility warnings before handing over prizes. Repeating schedules follow UTC, so their local hour can change with daylight saving time.

Starboard

Open Community → Starboard and choose New board.
Select a destination channel and an existing, user-created incoming webhook.
Choose a reaction emoji, minimum reactions, and posting mode: every qualifying message, the current leader, or a daily or weekly winner.
Set source channels and voting rules. For scheduled winners, check the board’s timezone and posting time.
Review the sample preview and create the board. Members nominate messages by reacting with its emoji.

Check who can see the destination. Leaving Included channels empty allows all eligible channels Rova can read, including role-restricted channels. Choose specific sources if more people can see the destination.

Tracking begins with reactions Rova observes; creating a board does not scan old channel history. Refresh tracked posts checks known messages. Scores can update, but a highlight keeps the text and media it had when first posted.

Sticky messages

Keep a reminder, guide or useful link near the bottom of a channel. After members post, Rova waits for the chosen delay, sends the sticky again and removes her previous copy. Bot and webhook messages don’t trigger a refresh, and mentions in the sticky don’t send notifications. This feature works without AI.

Open Roles & Automation → Sticky Messages and add a message. Choose a channel and enter the text, an embed, or both.
Set the refresh delay from 10 to 300 seconds. Check the preview. You can also import a message design with text and one supported embed.
Save the current message, then choose Publish saved message. Saving alone does not post it. Saving changes to an active sticky stops refreshes until you publish those changes.

Use Pause to stop refreshes while keeping the message and settings. Resume starts refreshes after new activity when the saved and published versions match. Stop tracking removes the saved setup and leaves the last message in Discord; delete that message in Discord if you no longer want it.

Each server can have up to 25 sticky messages, with one per channel. Use a different channel from your Wordle sticky. Rova needs View Channel, Read Message History and Send Messages, plus Embed Links for an embed. A thread needs Send Messages in Threads instead.

If a refresh fails, read the saved error. If delivery is uncertain, Publish checks recent messages before proceeding and never sends another copy automatically. Check the channel before stopping tracking. If someone deletes the tracked sticky, Rova pauses it; use Publish to create a replacement.

Welcome & boosters

Welcome new members

Open Welcome & Rewards → Welcome, select a channel, and edit the message and preview. Start with text and an embed, or import a Components V2 message. Save when it looks right.

Welcome {{mention}} to {{guild}}!

Use {{mention}} for the new member, {{guild}} for the server name, and {{membercount}} for the member count. The editor’s How to use placeholders guide lists the other supported values.

Thank your boosters

Open Boosters for one workspace with Rewards, Personal roles and Members. In Rewards, expand New boost thank-you to choose its channel and customize the message. Text, embeds and imported Components V2 layouts remain available.

Use Members to find someone and review their recorded history. Corrections are confirmed and applied separately from server settings. Switching tabs keeps both drafts; returning to Rewards or Personal roles restores the server settings Save and Discard controls.

Reward milestones and leaderboard

Under Boosters → Rewards, choose a reward notification channel and add the rewards your server offers. Expand a reward to change its required months, name or delivery method. An Automatic role reward assigns your selected role. A Manual reward opens a claim ticket; staff confirm delivery in that ticket after giving the reward. Opening a ticket does not count as delivering a reward.

Reward announcements lets you choose the embed color and preview the generated message. Rova names the actual reward, shows role rewards as received and links manual rewards to their claim tickets as awaiting delivery. There is one reward schedule; existing configured rewards carry into it.

The same saved schedule controls reward delivery and /boosters. Each milestone is awarded once per tracked boosting streak. Removing one does not take back roles already awarded. An empty schedule leaves the leaderboard available without promising rewards.

Staff with Manage Server can post /boosters for the server. The leaderboard uses a PNG with Rova's website fonts, the server icon and member avatars. Only the person who ran the command can use its buttons. Previous and Next replace the image in that message, showing five members per page. Everyone viewing the message sees the selected page. The buttons keep working after a bot restart.

The dashboard lets you choose a theme color and whether the leaderboard shows boost start dates, received rewards, the next milestone and grace-period notices. The image uses softer shades of your color for borders, rank badges and card backgrounds, with readable text and distinct styling for the top three. Manual rewards count as delivered only after staff confirm them in the claim ticket. Repeated rewards are grouped with a count, different role rewards stay separate, and upcoming rewards share their next milestone date. Long lists show how many additional rewards could not fit. Existing reward roles without a delivery record are labeled role held; pending claims stay separate. Names inside the image are not clickable. If an image cannot be generated, Rova displays a text leaderboard instead.

Custom roles

Before members create a personal role, an administrator must choose where custom roles belong in the server’s role list. The dashboard also controls who can customize a role and whether sharing is enabled.

Under Custom role placement, choose a role under Place custom roles below before members create personal roles. Choose the bot's highest role or a role below it. New roles appear directly below your selection; existing roles move there when customized. Saving the setting alone does not move existing roles. Clearing it prevents new role creation, while existing roles keep their placement. If the selected role is deleted or moved above the bot, update this setting.

Use /role claim in the configured customization channel to create or update a personal role. Use /role icon image: to upload an icon, and /role clear to remove the icon. Clearing an icon does not delete the role. Discord server capabilities still determine which icons and enhanced color styles are supported.

In Personal roles, expand Personal-role embed color to style role messages without changing anyone's role color. Expand Access without boosting to select roles that can customize and share a personal role without boosting. The customization channel still applies. Booster rewards require actual boosting.

Share a custom role

In the dashboard, turn sharing on or off, choose the recipient allowance and customize the invitation message. The default allowance is two recipients per owner, counting pending invitations and accepted gifts together. An uploaded role icon appears on the invitation.

Use /role share and select the members to invite. Boosters and members with a configured bypass role can share their own personal role.
Rova posts one invitation with Accept and Decline. Only the named recipients can operate those buttons, each for their own decision. The same invitation updates as members respond.
Recipients receive the role only after accepting. Unanswered invitations expire after 24 hours; accepted gifts remain until removed or the owner loses eligibility.

Owners use /role unshare to select from current recipients and pending invitations, rather than the whole server. Recipients use /role remove to leave an accepted role, even if sharing has since been switched off. Losing booster eligibility ends sharing unless the owner still has a qualifying bypass role.

/role help lists the options available in your server. These slash commands work without AI. Mentioning Rova to open the guided customization panel requires natural-language access, which is coming soon for Alpha servers.

/boosters lets staff with Manage Server post the server’s boosting leaderboard for members to browse. /welcome preview and /booster preview are private previews. Their test commands send a real message to the configured channel. A test message does not create an actual Discord boost.

Role categories & header sync

Heading roles organize a member’s role list. Rova adds a heading when the member has a role in that category, and removes it when they have none.

In Discord’s role settings, create a heading role with no permissions. Place Rova’s highest role above it.
Open Roles & Automation → Role Categories and enable role category synchronization.
Choose Add category, select the heading, and select the member roles it groups.
Review Preview, save, then choose Sync now to apply the saved setup to existing members.

Later role changes are checked automatically. Turning the feature off stops future changes and keeps existing headings. Removing a category from the configuration also leaves its existing heading assignments in place.

Use explicit categories for a new setup. Legacy automatic grouping is also available for servers already using separator roles; its preview shows which roles it groups. Wait for an in-progress synchronization to finish before starting another.

Server representation

In Welcome & Rewards → Server Representation, choose a reward role and announcement channel. Enable matching for approved custom-status phrases, a server tag, or both. A member qualifies when any enabled requirement matches. Save before choosing Update existing members; review whether that scan should announce new matches.

Leave status phrases blank to accept known invites for this server. A tag can use this server or an explicitly selected source server. Rova manages only the reward assignments it owns and needs Manage Roles with its role above the reward. Members can hold higher roles than Rova and still receive this reward.

Discord hides offline and invisible custom statuses. An unavailable status does not prove that a member removed it: Rova preserves a last-confirmed status match until it has evidence. Visible removal of a tag-only match can still remove its managed reward.

Wordle

In Community → Wordle, set a five- to seven-letter answer, destination channel, and sticky message. Set and post today’s word updates the answer and posts in Discord. Clear today’s word removes the saved answer and attempts to remove its sticky; recorded scores remain.

Staff with Manage Server can also use /wordlesetup set, view, or unset. Members use /rwordle leaderboard daily or global; “global” means this server’s all-time scores, not shared scores across servers.

/rwordle submit image: reads a completed Wordle grid using AI image recognition. Screenshot submissions require that feature to be available and enabled; existing scores and word management remain usable without it. The game-day reset follows America/New_York, shown in the editor, rather than each administrator’s local midnight.

Silly and Misc.: nickname protection

Open Silly and Misc. → Nickname Protection, enable protection, and choose the members to protect. Configure a notification channel, an emoji, and the message template, then save. This feature works without AI.

Rova uses Discord’s audit log to identify someone else changing a protected member’s nickname and restores the approved nickname when allowed. Members may still change their own nickname. Give Rova View Audit Log and Manage Nicknames, and place its role above protected members.

Templates support {actor}, {member}, {nickname}, and {emote}. Use a Unicode emoji or an available custom emoji from your server. Turning protection off keeps the settings and stops enforcement; an unavailable emoji is not replaced with a different one.

Chat & AI controls

Chat and AI-assisted commands are coming soon as paid features. AI features are coming soon for Alpha servers. AI access and advanced video processing are currently limited to Ronova Mains and development testing. Alpha approval and dashboard settings do not enable them. See what’s planned; ordinary commands and features that don’t use AI remain separate.

On an eligible server, System → AI Controls holds the switches for Conversation, Passive conversation, Contextual reactions, AI content moderation, Natural-language moderation, and Wordle image recognition. Choose an available provider and model for each feature, then save.

AI switches default to on for an eligible server, but new servers start without direct or passive chat channels. Review the switches before selecting channels or enabling monitoring. Eligibility does not copy Ronova Mains’ channel configuration or grant permissions.

Turning Conversation off also stops its passive replies and contextual reactions. Turning an AI feature off preserves its configuration and disables related controls while keeping the page viewable. Turning AI moderation off pauses media checks, unapproved-media enforcement, moderation alerts and staff pings. YouTube and Reddit feeds continue without AI review; previously flagged items stay held for a staff decision. Configured text-keyword deletion, manual moderation and account-age protection remain available; account-age safety alerts are separate.

Under Rova Chat, choose channels for direct mentions and replies, then choose any channels where Rova can join in on her own. Set passive reply limits before enabling a busy channel. Staff with Manage Server can also use /rovatalk and /passivechat. Rova may reply or stay quiet, even when mentioned.

Natural-language moderation has its own channel list and staff permission checks. Mention requests for partner ads, tickets, bulk role changes and guided booster customization require natural-language access, including their confirmation steps. Commands such as /partner post, /ticket open and /role claim remain available without AI. Only include private staff or ticket channels if their members and administrators want Rova to take part there.

Logging, history & recovery

System → Logging lets you choose events and destinations for messages, members joining or leaving, member changes, server changes and voice activity. Choose a default log channel, then set a different channel for any group that needs one. Only checked events are sent. A group with neither its own destination nor a default channel stays off.

Message logs cover deletions, edits and purges. Edits show the before and after text when available, with attachment details and a link to the message. Rova cannot recover text that was not cached. Member logs cover roles, names, avatars, bans and timeouts. Server logs cover channels, threads, roles, server settings and emoji. Voice logs show members joining, moving and leaving.

Clear, consistent log entries

Member logs include the member’s mention, profile image and user ID when available. Join logs show when the account was created and when the member joined. Leave logs include the join date, time in the server and last known roles when that information is available. A missing date or role history is shown as unavailable; a departure alone does not prove a kick.

Changes use before-and-after values where available, including member names, roles, timeouts, channel settings and role permissions. Voice entries show the member and the channels involved. These mentions identify people without pinging them.

Choose a Default embed color to give all of your server event logs the same accent. Deleted messages use the same layout as the other logs, with deletion details and preserved attachments included when available.

Use staff-only channels because logs can contain private content. Ignore channels or entire categories to keep their activity out of these logs. Log destinations are excluded automatically. Server event logging works without AI; the separate Decision journal is available where AI chat is enabled.

Reply diagnostics record decision and delivery metadata. Retain generated drafts is a separate sensitive opt-in that can keep draft text, source snippets, and member identifiers; it requires the journal and reply diagnostics. It does not recover older drafts or change how Rova replies. Read the displayed retention limits before enabling it.

System → History shows settings activity and restore points where supported. Read which settings a restore affects and preserve current drafts first. Some changes, including reaction-role activity, are audit-only. Restoring settings does not reverse messages already published, moderation actions, prizes, or roles already awarded.

If a feature reports unreadable saved data, stop editing that feature and contact support with the visible error. Existing data is preserved for repair; do not try to clear it by deleting configuration. Leaving a server does not itself request data deletion.

Discord command reference

Type / in Discord and choose Rova to see your available commands. Each action checks your permissions when you use it. Commands marked AI-only also need the relevant AI feature to be available and enabled.

Partnerships: /partner: ad shares your own ad; post prepares an incoming ad; assign, unassign, list, remove, and role manage tracked partners and representatives. Partner-manager access is required for management actions.
Tickets: /ticket, /ticketblacklist: Only administrators and configured ticket staff use /ticket open; they can specify another member with user:. Other members contact staff through the server’s ticket panel. Administrators use /ticketblacklist add, remove, and list to control new member-created tickets.
Event forms: /submit: Members open the current day’s form in an event’s configured submission channel while that day is accepting entries.
Member tools: /user, /notes, /warn, /timeout, /untimeout: Use Moderate Members access. Notes supports view and add. Supply the member and reason requested by Discord; timeout durations accept values such as 10m, 2h, or 1d. Keep member overviews, notes, and history in staff-only channels.
Moderation: /kick, /ban, /unban, /massban, /purge: Kick and ban require their corresponding permissions; unban requires Administrator. Massban also requires the owner’s authorization. Purge requires Manage Messages and scans up to 100 recent messages with optional user, text, bot, embed, or attachment filters. Review the target, reason, and any confirmation before taking action.
Moderation setup: /monitor, /rovamodcommands: Manage Server access is required. Monitor’s setup requires AI moderation; channels add/remove/list/clear remain available for text moderation. Clearing the channel list means all accessible channels. Use /rovamodcommands set, unset, list, or clear to manage conversational moderation channels while natural-language moderation is enabled. Review the rest of your setup in Safety Settings and AI Controls.
AI-only conversation: /rovatalk, /passivechat: Staff with Manage Server can use /rovatalk set/unset/list/clear for direct-reply channels. Use /passivechat enable/disable/list to choose where Rova can join in on her own, and debug to check its status.
Welcomes: /welcome: Manage Server staff use channel and message to configure delivery, preview for a private preview, and test to send a real welcome message.
Boosters: /booster, /boosters: Manage Server staff configure the thank-you channel and message, choose a reward-channel, or use preview and test. Configure rewards and their announcement color in the dashboard's Boosters → Rewards workspace. Boosters posts the leaderboard. Preview lets you check the thank-you message privately before sending a test to the configured channel.
Booster administration: /boostersetup: Administrators use roleclaim-channel to set the allowed customization channel. streak-view, streak-set, and streak-clear inspect or correct a member’s saved reward streak without changing Discord’s native boost date.
Personal roles: /role: Eligible members use claim to create or customize their role, icon to upload an icon, clear to remove only the icon, and help for instructions. When sharing is enabled, share invites selected members and unshare lists current recipients for removal. Recipients must accept before receiving a gift and can relinquish it with remove. The server must support any requested role style or icon.
Feeds: /youtuberss, /redditrss: Manage Server staff use subscribe, unsubscribe, list, or test. Reddit also has leaks for that flair’s inclusion. Test previews an item; read feed availability before relying on automatic posts.
Wordle: /rwordle, /wordlesetup: /rwordle submit requires AI image recognition. leaderboard daily/global reads this server’s scores. Manage Server staff use /wordlesetup set/view/unset for the answer and sticky message.

Set up reaction roles, Starboard, sticky messages, giveaways, role milestones, nickname protection, appearance, and logging in the dashboard. Members then use the panels, reactions, and buttons you publish in Discord.

When something needs attention

My server is missing: On the install page, sign into the correct Discord account and check that you own the server or have Manage Server or Administrator permission. The dashboard requires Administrator permission and Rova must already be in the server. Refresh or sign out and back in after access changes.
A role won’t apply: Check Manage Roles, Rova’s position above the target role, and the feature’s eligibility rules. Reaction-role permission warnings do not block an administrator’s configured choice; missing, managed and unmanageable roles still cannot be assigned.
A message won’t publish: Check the destination permissions and selected webhook. Save pending edits first, then read the publication error before retrying.
The dashboard says newer settings exist: Your draft is still available. Review the saved version and resolve the differences before trying to save again.
A setting is disabled: Read its nearby explanation. It may need another setting, an available permission, or a feature that is enabled for your server.

When asking your server’s administrators for help, include the feature, the action you tried, and the visible error. Keep private ticket contents and account details out of public channels.

Open dashboard