Settings → Discord Integration

The Discord Integration surface is where you pair your Discord server to this AO Master guild, then configure how the two stay in sync. Unlike most Settings, this lives on its own dedicated channel — #Discord Integration under the MANAGEMENT sidebar group — instead of inside the Settings modal. Most owners visit it once during onboarding, then occasionally to refresh role mappings or rebuild the bot's pinned UIs.

For the deep walkthrough of installing the bot + running /guild pair on Discord, see Discord — Install + pair. For the regear/enlist flows on the Discord side, see Discord regear flow + Discord enlist flow.

Permissions

The channel requires Manage Integrations to open. Grant it carefully — this permission is the Discord-side admin lever (it gates pair / unpair, role + war-role mapping edits, Enlist pipeline config, and pinned-message rebuilds).

Before pairing — what you see

When the bot isn't paired to your Discord server yet, the page shows a three-step onboarding card:

1. Invite the bot to your Discord server — opens a Discord OAuth page. Pick the server, confirm the Administrator permission grant. (The bot needs Administrator because it manages channels, roles, permissions, and webhooks on your behalf.)
2. Run /guild pair in your Discord server — a short wizard creates 6 channels and links the bot to this AO Master guild. Takes ~2 minutes.
3. Come back to this page — once the wizard completes, refresh and the page expands into the full configuration view.

The deep walkthrough with screenshots of every wizard step is at Discord — Install + pair.

After pairing — what you see

After pairing succeeds, the page swaps to the full configuration view (not shown in the screenshot above — QuickStart Demo isn't paired). The post-pairing sections include:

• Connectivity — bot online status, paired Discord server name + ID, ping latency.
• Role mappings — pair each AO Master role to a Discord role. When a member's role changes on either side, the bot syncs it back to the other side.
• War role mappings — same but for war roles. Used so the bot's per-channel UI shows the right role chip on each member.
• Enlist pipeline config — how the [Enlist] button on the public Discord channel routes new applicants (which web enlist code to back it with, optional autoresponder, etc.).
• Per-member channel config — turn the per-member 🪪 <character> channel feature on/off + pick which subsystems write to it (regear status messages, kill notifications, etc.).
• Refresh pinned messages — manual rebuild of the bot's pinned UIs (panel embeds, channel headers) without unpaching. Useful after a bot update changes the embed format.
• Unpair — disconnects the bot. The Discord channels stay (and become inert — bot stops posting), but the link between this AO Master guild and the Discord server is broken. Re-pair to restore.

Setup Checklist for Discord-side regear

The #Request Regear Discord-side flow needs more than just pairing — it also needs the per-member channel system on + war-role mappings filled in + the Enlist config set up if you want join-via-Discord to work. The page surfaces this as a checklist with deep-link buttons to the right section.

For the actual workflow of submitting / reviewing regears on Discord, see Discord regear flow.

Cross-links

• Discord — Install + pair — full deep-dive on inviting the bot + running the wizard.
• Discord — Channels overview — what the 6 channels the wizard creates do.
• Discord — Slash command appendix — full reference of /whoami, /link, /unlink, /enlist *, /regear *, /guild *, etc.
• Member enlist flow (web + Discord) — the join flow that this page's Enlist config feeds.

Last reviewed

Walked as demo01 (Owner of QuickStart Demo) on 2026-05-24 against commit 7dd04f1b. QuickStart Demo isn't paired to a Discord server, so the screenshot shows the three-step onboarding card. The post-pairing configuration UI is captured separately on the Discord Guide pages.