Frequently asked questions

Open the invite link and select a server where you have the Manage Server permission. Approve the requested permissions, and Nexumi joins within a few seconds.

After inviting, move the Nexumi role above any roles it should manage and open the dashboard to enable the modules you want.

Yes. All core features are available for free. A Premium tier only raises certain limits (more custom commands, feeds, and backups). Premium is assigned manually by the operator; there is no payment step required to use the bot.

Nexumi requests a broad permission set on invite so every module works out of the box (for example Ban Members, Manage Roles, Manage Channels, Manage Messages). You can restrict what it can do through Discord role settings, but some modules will stop working without their required permissions.

Not for basic commands. For most modules (welcome messages, tickets, leveling rewards, logging, etc.) you enable and configure them in the dashboard first. Set the server language and timezone early, since replies and time-based features follow those settings.

Type /help in your server for an auto-generated overview grouped by module, or open the full command reference in the documentation.

Each module can be turned off per server. If a command reports that its module is disabled, enable that module on the Modules page in the dashboard.

Yes. On the Commands dashboard page you can enable/disable each command, allow or block it per channel or role, and set cooldowns. There are also global channel whitelists and blacklists.

Administrative command responses are ephemeral by default, so configuration and moderation output stays private to the person who ran the command.

No. Nexumi uses only Discord slash commands, context menus, buttons, select menus, and modals.

Discord only lets the bot act on members and roles below its own highest role. Move the Nexumi role above the target roles, and make sure it has the matching permission (for example Ban Members for /ban).

They are stored persistently and run on a job queue, so a temp-ban expires and unbans on schedule even if the bot restarts. Timeouts are capped at Discord's 28-day maximum.

Every ban, kick, timeout, and warning creates a case with an ID. Use /case view to inspect it, or browse and search all cases in the dashboard. Cases can be edited or deleted by moderators.

You configure rules (spam, mass mentions, caps, invite/external links, word filter, duplicates, emoji spam, Zalgo, phishing) each with its own thresholds, action, and role/channel exceptions. Anti-raid and anti-nuke protections react to join spikes and destructive admin actions.

Sign in with Discord at the dashboard. You will see only the servers where you have Manage Server, plus any granted through role-based access rules.

Make sure Nexumi is actually in that server and that your Discord account has the Manage Server permission there. If you just changed permissions, sign out and back in so your server list refreshes.

Yes. You can grant specific roles access to specific dashboard modules — for example, letting moderators see only Moderation and Tickets.

The dashboard uses a sticky save bar. Changes are only stored after you press Save; you can also discard them. Validation errors are shown inline and must be resolved before saving.

Depending on the modules you enable, this can include Discord IDs, module and server settings, moderation cases, and (where a module needs it) message content or metadata. See the privacy policy for the full breakdown.

Use /gdpr delete confirm:true in Discord, or contact the operator using the details in the legal notice. Deletions are logged for compliance.

Only where a feature requires it (for example logging deleted messages or ticket transcripts). The snipe feature is disabled by default, and log retention is configurable per server.

Check the status page for shard status and incidents. If everything is green, confirm the bot has access to the channel and that the relevant module and command are enabled.

Commands can take a short while to register after inviting the bot. Try again after a minute, and make sure the bot has the Use Application Commands permission in the channel.

Join the support server — we are happy to help and to hear feature requests.