Integrations & Discord

All members can open Integrations (/g/{slug}/integrations). The page has two parts:

• Connection — the Discord server link and which roles may run bot commands. Officers and leaders manage this.
• Membership — how members get verified. Leaders choose one of two paths.

An invite link works under either path, and without Discord at all.

Connection

Link your Discord server

1. Open Administration → Integrations (or finish Guild setup onboarding).
2. Add bot to server, then run /link-server guild_id:<your guild UUID> in Discord (copy the command from the Discord server row). Leaders and officers on the website can link this way.
3. Without guild_id, /link-server still returns a website link to pick your guild (legacy flow).

If setup did not finish linking, confirm the Discord server ID on the Discord server row matches this AlbionZVZ guild.

Command permissions

Pick the 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).

One setting, two jobs. On the Discord roles verification path, these same member roles are what gate /register. The page marks the row when that is the case. On the in-game roster path they only control bot commands.

If commands still do not appear for a role after saving, a server admin can allow that role in Discord directly (works immediately, no AlbionZVZ deploy required):

1. Open Discord → Server Settings → Integrations → AlbionZVZ → Manage.
2. Under Roles and Members, add the role (for example Council), or unsync a command such as /cta and allow that role for it only.
3. Confirm members with that Discord role can see and run the command.

Membership: choose a verification path

Leaders pick one path. The page shows which one is active and, underneath it, only that path's options. Switching paths is not destructive — the other path's settings are kept and marked inactive until you switch back.

Path 1 — In-game roster

Members verify against your Albion guild roster through the game API. Options under this path:

1. Albion 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.
2. Allied guilds and alliances — optional.
   • Approved in-game guilds (up to 50) — mass or sister guilds with their own Discord roles. Members on those rosters can /register after 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).
3. Discord roles on register — optional. Grant Discord roles when a member passes verification, with optional Discord role auto-remove (scheduled about every 12 hours) and manual roster prune. This only grants roles after /register; it does not control who can run /cta. Use Command permissions for command access.
4. Discord nicknames — optional. Sets a member's Discord server nickname to their verified Albion character name when they run /register, with an optional prefix. Set the prefix for your primary guild here; set a different prefix per approved guild or approved alliance on their own row in step 2, so allied guilds can carry their own tag. Applied once, at registration — members can rename themselves afterward, and existing members need a leader to re-run /register or wait for a future manual re-apply. Requires the bot to have Manage Nicknames in your server; the toggle checks this before turning on and tells you what to fix if it can't. The server owner and any member whose highest Discord role sits above the bot's are always skipped — that's a Discord limitation, not a bug.

Registration checks the primary roster first, then approved guild rosters, then approved alliance membership.

Path 2 — Discord roles

Members need a member-tier Discord role to run /register. No Albion API involved, and no in-game guild link is required.

The roles are the Member commands roles from Command permissions above — the same setting. If no member roles are set, /register is open to everyone in your server, and the page warns you.

If you previously linked an Albion guild, that link is kept but inactive on this path. The page says so, with a shortcut back to the in-game path.

Invite link

A shareable website link that works under either path, and for guilds with no Discord server at all. Manage it on Administration → Invite.

Elsewhere

Members link Albion characters on Account settings (/dashboard/profile).

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 and which verification path is active. Ask an officer to change bot permissions, or a leader to change the verification path.