Documentation / Overview / Getting Started
/setup Required permission: Administrator

- 1. Invite & Authorize the Bot
Invite the bot with server Administrator permission and move its role to the top.
https://discord.com/oauth2/authorize?client_id=1527276218007687168&permissions=8&integration_type=0&scope=bot+applications.commands - 2. Run Auto Setup
Build the log category, audit channels, and access rules with a single command.
/setup - 3. Monitor Protection Live
View panic mode and the thresholds with /antiraid.
/antiraid
Aegis Guard brings moderation, logs, tickets and giveaways together in one Discord bot. When you type /setup, it creates the log channels, roles and core protections for you.
Auto Setup (/setup)
If there is no log category installed on the server, Aegis creates the aegis-logs category visible only to staff and 5 log channels. It also opens public, read-only welcome and announcements channels and the tickets category. 15 log types are collected in these 5 channels; each type can be redirected to a separate channel from the panel:
- guvenlik-log
- AutoMod, Anti-Raid, Anti-Nuke, Entry Gate, token leaks and channel changes.
- mod-log
- Ban, kick, mute, warn and voice moderation.
- uye-log
- Joins and leaves, nicknames, roles, invites and voice channels.
- mesaj-log
- Deleted and edited messages.
- ticket-log
- Opened and closed tickets, transcripts.
/setupWhen a user with Administrator permission on the server runs this command, Aegis isolates all permissions in the background and activates its protection.
Critical: Role Hierarchy Rule
In the Discord security model, a bot can only interfere with roles and members that are lower than its own role. For Anti-Nuke protection to be able to ban attacking administrators, the Aegis Guard role must be positioned above all other administrator roles in Discord Server Settings > Roles.
- Drag the Aegis Guard role to the very top of the list (just below the Server Owner role).
- Ensure the bot's 'Manage Roles' and 'Ban Members' permissions are enabled.