Choose and configure server modules
Enable the features your server uses and keep everything else off.
Start with a small module set
Section titled “Start with a small module set”Axon Core and Diagnostics cover installation and health checks. Add one operational module at a time so staff can confirm its channels, roles, and behavior before enabling the next one.
Configure a module
Section titled “Configure a module”- Open the server’s Setup guide or Modules list. Turn on a module you need, then open its Settings.
- Choose the Discord channels and roles used by that feature.
- Review any permission warning shown beside a field.
- Save a draft and publish it. Enabling a module and publishing its settings are separate actions.
- Run the module’s test action where one is available, or try its documented Discord workflow before announcing it to members.
The setup checklist tracks whether you have chosen features, published their settings, and run a diagnostic scan. A completed checklist does not prove every channel or workflow works; test the features you chose.
Set up Event Logging channels
Section titled “Set up Event Logging channels”Open Event Logging and select Create channels to add the private 📜・LOGS category. Choose a staff role if moderators need access; otherwise server administrators and Axon can see the channels. Review the event routes, then select Save and publish. The setup enables Event Logging and routes events to the matching channels.
Axon logs changes to channels, roles, invites, messages, members, voice, scheduled events, stages, emoji, stickers, soundboard sounds, threads, webhooks, and bots. It also logs Discord and Axon AutoMod actions, Axon application submissions, and Axon poll creation and closure. Application answers stay out of Event Logging. Discord supplies only a channel-level update for webhooks, so that log won’t identify the exact webhook change.
Show deleted and edited message text is enabled when you use Create channels. Existing server configurations keep it off until an administrator enables it and publishes. With it on, the private Message Log shows deleted text and the before and after text for edits. Axon keeps up to 1,000 recent message snapshots per server for 24 hours so it can recover text from delete events. Older messages, messages Axon did not observe, and edits whose earlier version was unavailable are clearly labeled. Attachment names are shown when known. Message log entries and their pending delivery records are removed from Axon’s database after 30 days; copies already sent to Discord follow your server’s retention and permissions. Only dashboard users with Logs view access can open message details in Axon’s history.
Open Honeypot under Safety to choose a trap channel and a timeout, kick, or ban action. The setting starts off. Honeypot uses Event Logging, so enable that module on the same page before publishing. A regular member posting in the trap channel triggers the action, a moderation case, and an audit record. Bots, the server owner, and members with moderation permissions are exempt. Axon needs the relevant Discord permission and role position; if the action fails, the case and audit record show the failure. Triggering messages are removed when Axon can delete them. Route Discord AutoMod action to a log channel if staff want a separate alert.
The same page can post an Axon warning embed with a live 🍯 catch total, or attach the counter to an existing message sent by the active bot. The total is saved separately from the module setting, so disabling and re-enabling Honeypot or replacing a deleted counter message does not erase it. Wipe counter resets only the catch total after confirmation; moderation cases and audit history stay intact.
Set up applications
Section titled “Set up applications”Open Applications under Community. Create a form with questions, choose whether members answer in a Discord modal or by DM, and select the staff response channel. Use a private staff channel because responses posted there include applicant answers. Members can use /apply; you can also post a button or dropdown panel in a server channel.
Form rules can require or block roles, set a cooldown, and prevent more than one pending application per member. Reviewer roles can vote or decide from the response message. Accepting or denying a response can change the applicant’s roles and send a DM. The dashboard keeps the response queue and lets staff download a form’s CSV responses or a JSON backup. Failed Discord role changes and blocked DMs appear in the decision result; check the member’s roles and contact them directly if needed.
You can send a direct application invitation to a server member from an open form. The Applications page also shows Axon’s button polls, shared with Suggestions & Polls; enable that module to use them.
Set up sticky messages
Section titled “Set up sticky messages”Open Sticky Messages under Community. Choose a text channel and paste the ID of an existing message in that channel. Axon saves its text and embeds and posts a copy after the next channel message. Set a cooldown to limit reposts during busy conversations. The original source stays in Discord; Axon removes its previous copy when it posts a new one. The page shows the last delivery error if Discord rejects a repost.
Channel, role, and server updates show the fields that changed with their previous and new values where Discord supplies both states.
Existing servers keep newly added event types off until an administrator enables and routes them or runs channel setup. Each event has its own switch and destination; a missing destination means no delivery.
Disable without losing history
Section titled “Disable without losing history”Turning off a module stops its new actions. Existing audit entries, cases, ticket transcripts, and retained records remain subject to the server settings and Axon retention rules.