Add nyx to your server
nyx is a Discord ticket bot, automod bot, and moderation bot that requests only the permissions it needs — no Administrator access. Review what it uses below, then add it when you’re ready.
No Admin access
Only feature-specific permissions are requested. Never Administrator.
Privacy first
nyx never reads DMs or stores message content beyond configured logging.
Fully configurable
Every feature can be toggled from the dashboard. Disable what you don’t need.
Role hierarchy tip
For safety, place the nyx role below your admin and moderator roles, but above the roles of members it needs to moderate. This ensures nyx can manage regular users without ever having power over your staff.
Discord enforces role hierarchy strictly — a bot can only moderate members whose highest role is below the bot’s own role. Keeping nyx beneath your admins means it can never accidentally affect privileged users.
What happens when you install
Here’s what becomes available once nyx joins your server.
What nyx helps you manage
nyx covers the Discord workflows that usually require multiple bots.
Tickets and support
Run support panels, manage ticket routing, and keep cloud transcripts available for staff review.
Automod and moderation
Apply real-time rules, anti-ping protection, and moderation actions without command spam.
Logging and audit history
Track message, member, role, channel, and voice activity in one Discord logging bot workflow.
Per-server dashboard control
Configure each server from the web dashboard instead of memorizing long setup commands.
Permissions nyx requests
Each permission maps directly to a ticketing, moderation, logging, or transcript feature. Nothing extra.
Needed by the Logging plugin to identify moderation actors (for example, who kicked a member) instead of recording those events as generic leaves.
nyx needs to see configured support channels, ticket channels, and guild locations before it can respond or manage workflows.
Required for slash-command responses, ticket prompts, anti-ping notices, ticket logs, and general bot output.
nyx uses embeds for ticket headers, anti-ping messages, logs, and other structured responses.
Required for scheduled embeds and other announcement-style messages when a server intentionally configures nyx to ping @everyone, @here, or mention roles.
Needed for transcript attachments and future file-based support exports generated by the ticket system.
Required for transcript generation, moderation context, and ticket workflows that depend on earlier channel history.
Used by anti-ping when configured to delete mentions, and for controlled cleanup in ticket-related workflows.
Needed by Automod to place members in timeout when a rule is configured to escalate beyond warnings or message deletion.
Needed by Automod when a server configures a rule to remove a member from the server after matching a moderation policy.
Needed by Automod when a server configures a rule or escalation to ban a member after severe or repeated violations.
Required for creating ticket channels, applying permission overwrites, and deleting or archiving tickets when they are closed.