Welcome to Nuvon
A powerful, cross-server moderation bot built for Discord communities. Configure, sync, and protect — all in one place.
Inviting the Bot
Adding Nuvon to your Discord server takes less than a minute. Everything after that happens in the dashboard.
/invite command in a server that already has Nuvon. You need the Manage Server permission to add a bot to a Discord server.Required Permissions
Each permission below is needed by a specific feature. If you do not use that feature, the permission is not required — but granting them all during the invite avoids surprises later.
Nuvon's role must sit abovethe roles it manages in your server's role list. Discord does not allow a bot to ban, kick or assign roles that rank higher than its own — the action fails no matter which permissions you granted.
Steps to Invite
- Open the official Nuvon invite link.
- Select the target server from the dropdown.
- Review and confirm the requested permissions.
- Complete the authorization process.
- Drag the Nuvon role above the roles it should manage.
- Open the dashboard — the server now appears in your list.
Opening the Dashboard
Log in with Discord and pick a server. Which servers you see depends on what you are allowed to manage.
Login runs through Discord OAuth2 — Nuvon never sees your password. After logging in you land on the server selection, which lists every server where Nuvon is present and you have dashboard access.
Who sees a server
✅ Has access
- ›The server owner — always, and to every page
- ›Anyone holding a Discord role that a permission role points to
- ›Anyone added individually to a permission role
❌ No access
- ›Discord administrators without a permission role
- ›Moderators who were never given a page
- ›Servers where Nuvon is not present
Having Administrator in Discord does not grant dashboard access. Only the server owner starts with full access; everyone else needs a permission role, created on the Permissions page. This keeps dashboard access separate from Discord permissions.
Dashboard Basics
How the dashboard is laid out and how changes are saved. The same pattern applies to every feature page.
The Pages
The sidebar lists one page per feature. You only see the pages you are allowed to open — a page you have no access to simply is not there.
GeneralServer info, support key and data retentionCommandsTurn individual slash commands on or offLogging29 log types, each with its own channelSynchronisationMirror moderation to connected serversAnti-PingShield selected members from mentionsSticky MessagesKeep a message pinned to the bottom of a channelVoice SupportVoice-based support queue with private roomsBackupsSnapshot and restore channels, roles and settingsGatekeeperJoin roles, greetings, verification and join filtersPermissionsDecide who may open and edit which pageFeature Switches
Most sidebar entries carry a switch. It turns the whole feature on or off without discarding its configuration — flip it back on and your settings are still there. The switch is greyed out if you may view the page but not edit it.
Saving Changes
Command List
All 15 Nuvon commands are slash commands (/). This is the same list you find on the Commands page of the dashboard.
/banPermanently bans a user from the server. They cannot rejoin until they are unbanned.
/unbanLifts a ban, restoring the user's ability to rejoin via an invite link.
/softbanBans and immediately unbans a user. The ban deletes their recent messages, the unban lets them return — a purge without lasting exclusion.
/multiple-banBans several users at once from a list of user IDs. Built for raids, where speed matters more than individual cases.
/kickRemoves a user from the server. They can rejoin with a new invite.
/timeoutTemporarily stops a user from sending messages, reacting or speaking in voice channels.
/timeout-removeEnds an active timeout early and restores the user's ability to interact.
/purgeBulk-deletes a number of messages from a channel. Discord does not allow bulk deletion of messages older than 14 days.
/role addAssigns a role to a member.
/role removeRemoves a role from a member.
/setnickChanges a member's nickname on this server.
/slowmodeSets or clears the slowmode interval of a channel.
/embedPosts a formatted embed into a channel — for rules, announcements or info panels.
/verifyPosts the Gatekeeper verification message into a channel. Requires the Verify Module to be configured.
/inviteReturns the official Nuvon invite link so you can add the bot to another server.
Enabling Commands
Every command can be switched off individually on the Commands page of the dashboard.
Each command has its own switch. Activate All and Deactivate All flip the entire list at once — useful when you only want two or three commands available. As with every page, the change takes effect once you press Save Changes.
A disabled command disappears from Discord's command list entirely — members will not see it while typing /. It is not hidden, it is unregistered, so nobody can run it by guessing the name.
General
The landing page of every server: what Nuvon knows about it, and how long that knowledge is kept.
Server Information
Support KeyYour server's identifier when contacting Nuvon support. Treat it as private.Server NameThe name Discord currently reports for this server.Server IDThe Discord snowflake of this server — useful for support and backup imports.Data Handling
Two controls decide what happens to your configuration. Both apply to this server only.
Delete Data BehaviorWhat happens when Nuvon is removed from the server: Immediately wipes the configuration at once, After 30 Days keeps it as a grace period so a re-invite restores everything.Delete all dataWipes this server's configuration right now: log settings, anti-ping, synchronisation and command configuration.Deleting data cannot be undone. If you want to keep the structure of your server, create a backup first — backups live separately from the configuration data this button removes.
Logging
29 log types across 9 groups. Every type can be switched on individually and sent to its own channel.
Logging is not one switch and one channel. Each log type carries its own channel, so member joins can land in a public channel while moderation actions go to a staff-only one. A type that is switched off is not recorded at all.
One channel per log type
Pick the group in the dashboard, enable the types you care about, and set a target channel for each. Only text channels can be selected.
Log Groups
Channel LogsCreated, deleted, updated, permission changes — 4 typesRole LogsCreated, deleted, updated — 3 typesModeration LogsBan, unban, kick, timeout added and removed — 5 typesMember Update LogsRole changes and nickname changes — 2 typesEmoji LogsCreated and deleted — 2 typesInvite LogsCreated and deleted — 2 typesMessage LogsDeleted, edited, reaction added and removed — 4 typesWebhook LogsCreated, removed, updated — 3 typesVoice LogsChannel join, leave and switch — 3 typesA log type without a channel produces nothing. Nuvon also needs permission to write in the target channel — if a log never appears, that is the first thing to check.
Synchronisation
Nuvon's flagship feature — mirror moderation from this server to up to 10 connected servers.
One server acts as the main guild, the connected ones as subguilds. A ban issued in the main guild is carried into every subguild that has ban syncing enabled. Server networks stop repeating the same moderation work in five places.
Per subguild, per action
Each connection is configured separately. One subguild can receive bans only, another bans and timeouts — nothing is all-or-nothing.
Synced Actions
Settings per Subguild
Sync BansCarry bans from the main guild into this subguildSync UnbansCarry unbans over as well, so a lifted ban is lifted everywhereSync KicksKick the member in this subguild tooSync TimeoutsApply timeouts of the same duration hereLog ChannelWhere this subguild records what arrived from the main guildImporting Existing Bans
Synchronize Bans
Rules
✅ Possible
- ›Up to 10 subguilds per main guild
- ›Different actions per subguild
- ›A subguild can leave the group on its own
❌ Not possible
- ›A server as main guild and subguild at once
- ›The same subguild in two different groups
- ›Connecting a server you have no access to
You can only connect servers you can open in the dashboard yourself. Without that rule, anyone could attach a stranger's server as a subguild and ban members there through their own main guild.
Anti Ping
Shield individual members — owners, founders, celebrities — from being pinged directly.
Anti Ping is not a spam filter. It protects a short list of named people: when someone mentions a protected member, Nuvon steps in and points the conversation towards the support team instead. Useful wherever a handful of people would otherwise be pinged all day.
Settings
Protected UsersUp to 3 members who should not be pinged directly. Search them by name — no IDs to copy.Log ChannelWhere Anti Ping events are recorded. Required as soon as one user is protected.Channel WhitelistUp to 4 channels where pings are ignored, e.g. a staff channel.Role WhitelistUp to 3 roles whose members may ping freely, typically your moderator roles.Without a log channel the configuration cannot be saved while users are protected — the system refuses to run silently.
Sticky Messages
Keep one message glued to the bottom of a channel, so it stays visible no matter how busy the conversation gets.
How It Works
Nuvon creates a webhook in the channel and reposts your content whenever a new message pushes it out of view. The previous copy is removed, so the channel never fills up with duplicates. One sticky message per channel.
Two Formats
💬 Message
- ›Plain text
- ›Up to 2000 characters
- ›Looks like a normal chat message
🖼️ Embed
- ›Title, up to 256 characters
- ›Content, up to 4096 characters
- ›Accent colour of your choice
Webhook Appearance
Because the message is posted through a webhook, you control the name and avatar it appears under. Set them to your server's name and icon and the sticky message reads as an official notice rather than a bot post.
NameDisplay name of the webhook posting the messageIcon URLAvatar shown next to the messageActivePause a sticky message without deleting its configurationVoice Support
A support queue that runs on voice channels: members wait in a room, your team picks them up, Nuvon opens a private channel for the conversation.
The Flow
- A member joins the waiting room.
- Nuvon notifies the support team and, if configured, pings the support role.
- A team member accepts the case.
- Nuvon creates a private voice channel under the support category and moves both parties there.
- When the case is closed, the temporary channel disappears again.
Settings
Waiting RoomVoice channel where members wait to be picked upSupport CategoryCategory under which the temporary support rooms are createdNotification ChannelText channel for status updates — case opened, case closedSupport Team RolesUp to 5 roles allowed to handle cases. They automatically gain access to the temporary rooms.Role to PingRole mentioned when a new request arrivesPing Role ChannelText channel holding the toggle button for that pingPing MessagePosts the message with the toggle button, so the team can mute pings themselvesAuto-move StaffPull a team member into the support room on accept, even if they are already in another voice channelWaiting Room Sound
You can upload an audio file that plays while someone waits — a greeting, an announcement, or music.
Accepted formats are MP3, OGG, WAV, FLAC and M4A, up to 50 MB per file. One sound per server; uploading a new one replaces the old.
Backups
Snapshot your server's structure and restore it later — after a raid, a botched restructure, or when setting up a second server.
Slots and Automation
Every server has 5 backup slots. Create a snapshot manually at any time, or let Nuvon do it once every 24 hours. With Delete oldest when full enabled the oldest snapshot makes room for the newest — without it, automatic backups stop once all five slots are taken.
Settings
Automatic daily backupsCreate a snapshot every 24 hoursDelete oldest when fullOverwrite the oldest backup once all 5 slots are usedLog channelPost a message here whenever a backup is createdRestoring and Sharing
♻️ Load
- ›Applies a snapshot to this server
- ›Recreates channels and roles
- ›Restores the settings stored in it
📤 Import
- ›Every backup has an ID
- ›Enter that ID on another server
- ›Copies the structure across servers
Backups cover channels, roles and settings — not messages and not members. Anyone who knows a backup ID can import it into a server they administrate, so treat the ID as confidential.
Gatekeeper
Everything that happens the moment someone joins: which roles they get, how they are greeted, whether they must verify, and which accounts are stopped at the door.
🎭 Join Roles
Up to 5 roles that every new member receives automatically, plus a separate set of up to 5 roles for bots. Combined with an unverified role this is what keeps newcomers out of your channels until they pass verification.
Join RolesUp to 5 roles applied to every new memberBot Join RolesApplied to bots instead of the roles above👋 Welcome and Bye Messages
Send an embed when someone joins or leaves. Both messages are configured the same way and can be switched on and off independently — a welcome without a farewell is perfectly fine.
ChannelWhere the message is postedTitleHeadline of the embedContentBody text, optionalImage URLImage shown in the embed, optionalAccent colourColour of the embed's left border, default #808080Placeholders
Title and content understand four placeholders. Nuvon replaces them with live values the moment the message is sent — so one text works for every member, forever.
${server}Name of this server${username}Name of the member who joined or left${userTag}The member as a clickable mention${memberCount}Number of members on the server after the join or leaveTitle: Welcome to ${server}!
Content: Hey ${userTag}, glad you made it — you are member number ${memberCount}.
Write the placeholders exactly as shown, including the braces. A typo is not reported as an error — the text simply appears verbatim in the message.
✅ Verify Module
Require new members to prove they are human before they get access. Nuvon posts a verification message; passing it swaps the unverified role for the verified one.
Verify ChannelWhere the verification message is postedLog ChannelWhere verification attempts are recordedVerified RoleGranted once a member passesUnverified RoleHeld by members until they verifyEmbedTitle, content, image and accent colour of the verification messageSend EmbedPosts the message into the verify channel — run this after configuringVerify Types
A single button press. Stops nothing but accidental joins.
A small calculation. Stops the simplest bots.
Pick the right image. Harder to automate.
A full captcha. The right choice while under attack.
Verification only keeps people out if the unverified role actually restricts them. Set the channel permissions so that unverified members can see the verify channel and nothing else — the role alone does not lock anything.
🛡️ Join Filters
Five independent filters examine every account that joins. Each one is switched on separately and has its own log channel and its own action — a young account can be logged while a bot is kicked outright.
No profile pictureAccounts still using Discord's default avatarBot filterAny bot joining the serverUnverified bot filterBots without Discord's verification badgeAccount age filterAccounts younger than the minimum age you setAccount name filterAccounts whose name matches your criteriaActions
Logs the join and does nothing else. Start here to see what a filter would catch.
Removes the account. It can return — with a new invite and a new attempt.
Removes the account permanently.
Permissions
Decide who may open and edit which page of the dashboard — without handing anyone Administrator in Discord.
Dashboard access is deliberately separate from Discord permissions. Being an Administrator in Discord grants nothing here. The server owner always has full access; everyone else gets exactly the pages you assign.
Permission roles
A permission role is a rule, not a Discord role. It says: everyone holding one of these Discord roles — plus these individually named members — may view or edit these pages.
Roles Tab
NameFree-text name, e.g. Moderators or Log TeamDiscord rolesEveryone holding one of these roles is covered — including members who receive the role laterIndividual membersNamed members, searched by name. Useful for a single person who needs one page.PagesPer page: View and Edit. Edit always includes View.👁️ View
- ›The page appears in the sidebar
- ›All settings are readable
- ›Every control is greyed out
✏️ Edit
- ›Everything View allows
- ›Settings can be changed and saved
- ›Includes the feature switch in the sidebar
Members Tab
Search any member to see what they are actually allowed to do, and through which roles they got it. This tab only reports — to change something, edit the role that grants it. A permission for a single person is simply a role containing only that person.
When Changes Take Effect
Saving or editingImmediately — anything you change here applies to the affected members at onceDiscord role removedEditing is blocked immediately; the page may stay visible for up to 60 secondsLeaving the serverSame as above — access ends, the display can lag by up to a minuteGranting Edit on the Permissions page itself lets that person hand out every other permission, including to themselves. It is delegable on purpose — but give it to as few people as possible. The dashboard warns you when you tick that box.
Overview
Every log type Nuvon can record, in the same groups you find on the Logging page of the dashboard.
Each type is switched on individually and writes to its own channel. Nothing is recorded until you enable it — Nuvon does not log by default.
29 log types in 9 groups
Enable only what you need. A quiet, useful log channel beats a complete one nobody reads.
A type without a target channel produces nothing, and Nuvon needs permission to write in the channel you pick. Only text channels can be selected.
Channel Logs
Structural changes to the channels of your server.
channelCreateA new channel was created — text, voice, category or forum.
channelDeleteA channel was permanently deleted. The entry keeps name and ID after the channel itself is gone — the record you need when a deletion was not planned.
channelUpdateA channel's properties changed — name, topic, slowmode, NSFW flag or category.
channelPermissionUpdateThe permission overwrites of a channel changed. Tracked separately from other channel updates because this is how a channel quietly becomes visible — or invisible — to a role.
Role Logs
The lifecycle of your roles: created, deleted, changed.
roleCreateA new role was created.
roleDeleteA role was deleted. Its last known properties are kept in the entry.
roleUpdateA role changed — name, colour, permissions, hoisting or mentionability. Worth enabling on any server where several people can edit roles: a permission added here is easy to miss otherwise.
Moderation Logs
Every moderation action — whether it came from a Nuvon command, another bot, or straight from the Discord client.
memberBanA member was banned.
memberUnbanA ban was lifted.
memberKickA member was removed from the server without a ban.
timeoutAddedA member was timed out and can no longer write or speak.
timeoutRemovedA timeout was ended early.
Member Update Logs
Changes to a member's profile on this server.
roleChangeA member gained or lost a role. The entry that answers the question of who handed out that moderator role.
nicknameChangedA member's nickname changed on this server.
Message Logs
Deleted and edited messages, plus reactions.
messageDeleteA message was deleted — by its author, a moderator or Nuvon itself.
Discord only hands out the content of messages the bot still has in its cache. For older messages, the entry contains metadata but no text — that is a limit of the platform, not a setting.
messageUpdateA message was edited. The entry shows the version before and after.
reactionAddA reaction was added to a message. Useful for reaction-based roles or votes.
reactionRemoveA reaction was removed from a message.
Voice Logs
Who joins, leaves and moves between voice channels.
channelJoinA member joined a voice channel.
channelLeftA member left a voice channel.
channelSwitchA member moved from one voice channel to another — on their own or because they were moved.
Emoji, Invite & Webhook Logs
Three smaller groups covering emojis, invite links and webhooks.
emojiCreatedAn emoji was added to the server.
emojiDeletedAn emoji was removed from the server.
inviteCreateAn invite link was created. Together with inviteDelete this is how you find out where a wave of new members came from.
inviteDeleteAn invite link was deleted or expired.
webhookCreatedA webhook was created in a channel.
webhookDeletedA webhook was deleted.
webhookUpdatedA webhook was changed — name, avatar or target channel.
Dashboard Overview
The Nuvon Web Dashboard is the control panel for every setting the bot offers — across all your servers, in one place.
One Panel. Every Server.
Log in with Discord, pick a server, configure. Every feature documented here has a page, and every page follows the same layout: settings at the top, save bar at the bottom.
What the Dashboard Does
Visual Configuration
Ten pages, one per feature. Channels, roles and members are picked from searchable lists — no IDs to copy, no commands to memorise.
Granular Access
Per page and per person: view only, or view and edit. Discord's Administrator permission grants nothing here — only the server owner starts with full access.
Every Server in One Place
Switch between all servers you have access to from the header, without logging in again.
Applied Immediately
Saved changes reach the bot right away. No restart, no waiting, no confirmation step.
Explicit Saving
Nothing is written while you type. A save bar appears as soon as something changed, and leaving the page without saving discards it.
Data Under Your Control
Decide whether your configuration is deleted immediately or kept for 30 days when Nuvon leaves — or wipe it yourself at any time.
Requirements
🔑 Access
- ›A Discord account (login via OAuth2)
- ›Nuvon present in the server
- ›Server owner, or a permission role granting at least one page
🌐 Technical
- ›A current browser
- ›JavaScript enabled
- ›Nothing to install
Data Handling
What Nuvon stores, how long, and how you get rid of it.
Nuvon stores configuration, not conversations. Log entries are posted into your own channels and live in your server, not in a Nuvon database. What is stored is the settings you make plus the IDs those settings point to.
Stored per Server
ConfigurationYour settings for every feature: channels, roles, switches, textsIDsDiscord IDs of the channels, roles and members your settings refer toBackupsSnapshots of channels, roles and settings — only ones you created yourselfPermission rolesThe rules deciding who may open which pageDeleting Data
ImmediatelyConfiguration is deleted as soon as Nuvon is removed from the serverAfter 30 DaysConfiguration is kept for 30 days, so a re-invite within that window restores everythingDelete all dataWipes this server's configuration right away, without removing the botBoth options live on the General page and apply to that server only. Deletion cannot be undone — create a backup first if you want to keep the structure of your server.