Documentation
Integrations & Discord
Connect Discord and configure bot commands.
All members can open Integrations (/g/{slug}/integrations). Only officers and leaders can change bot connection and command tiers.
Connect Discord
- Open Administration → Integrations (or finish Guild setup onboarding).
- Add bot to server, then run
/link-server guild_id:<your guild UUID>in Discord (copy the command from onboarding). Leaders and officers on the website can link this way. - Without
guild_id,/link-serverstill returns a website link to pick your guild (legacy flow).
Link server to guild
During onboarding, copy /link-server guild_id:… from step 2 and run it in your Discord server while signed in to AlbionZVZ with the same Discord account.
If setup did not finish linking:
- On Integrations, use Link server or run
/link-server guild_id:<uuid>in Discord. - Confirm the Discord server ID matches this AlbionZVZ guild.
Command tiers
On Integrations step 2, officers pick Discord roles (for example @Council) that may run officer and member bot command groups. This is not the same as your AlbionZVZ website officer role: members need the Discord role you select here to run commands like /cta, even if they are officers on the website.
- Officer commands —
/cta,/flash-mass,/events, and similar staff tools. - Member commands —
/register,/content-ping,/build, and similar.
Leave officer roles empty to allow only members with Manage Server or Manage Events on Discord. Role picks apply when someone runs a command (may take up to about one minute to propagate).
If commands still do not appear for a role after saving step 2, a server admin can allow that role in Discord directly (works immediately, no AlbionZVZ deploy required):
- Open Discord → Server Settings → Integrations → AlbionZVZ → Manage.
- Under Roles and Members, add the role (for example Council), or unsync a command such as
/ctaand allow that role for it only. - Confirm members with that Discord role can see and run the command.
Role sync (Integrations step 4) only grants Discord roles after /register onboarding — it does not control who can run /cta or other bot commands. Use step 2 for command access.
In-game guild and roster sync
Leaders only (steps 3–4 on Integrations):
- In-game guild — search and link your Albion Online guild; optionally require linked in-game accounts and remove members no longer on the roster. If members join without linking a character, use Remove unverified from website on that step.
- Approved in-game guilds (up to 50) — list mass or sister guilds with their own Discord roles. Members on those rosters can
/registerafter the primary roster check. - Approved alliances (up to 5) — fallback when a character is not on the primary or approved guild rosters but their in-game guild belongs to a listed alliance. Use Add primary guild's alliance or search by member guild name (not alliance name) to find an alliance.
- Approved in-game guilds (up to 50) — list mass or sister guilds with their own Discord roles. Members on those rosters can
- Role sync — pick Discord roles for your primary in-game guild, then enable auto role sync, optional Discord role auto-remove (scheduled about every 12 hours), and manual roster prune.
Members link Albion characters on Account settings (/dashboard/profile). Registration checks primary roster first, then approved guild rosters, then approved alliance membership.
Timer killboard on archived events also uses the linked in-game guild from Integrations.
Member view
If you are not staff, you can still read Integrations to see whether Discord is connected. Ask an officer to change bot permissions.