Member enlist flow

How someone goes from "interested in joining your guild" to "member with roles + character linked". The flow has two surfaces — the web flow + the Discord-bot flow. The two work in parallel; applicants pick whichever they prefer.

Web flow

1. Recruiter creates an enlist link on Settings → Enlists. The link looks like https://ao-master.com/enlist/<code>.
2. Recruiter shares the link (in Discord, Reddit, an Albion forum thread, wherever).
3. Applicant clicks the link → public-facing landing page with guild name, icon, description, and a Join button.
4. Applicant signs up / signs in to AO Master (if they don't have an account yet, they're walked through email verification first — see Sign up + verify email).
5. Applicant clicks Join → the application lands on #Join Requests for the guild's recruiters.
6. Recruiter reviews on #Join Requests → Approve (adds them to the guild with the Default Member Role) or Reject (with optional reason that's shown to the applicant).
7. Approved applicant lands on the guild's #Welcome channel. They link their Albion character (see Members — Link an Albion character) and start using guild channels.

Discord-bot flow

When the AO Master Discord bot is paired (Settings → Discord Integration) + Enlist pipeline configured, applicants can also use Discord:

1. Discord user clicks the [Enlist] button on the bot's pinned enlist message in your Discord server.
2. Bot creates a ticket channel scoped to that user — only the applicant + recruiters can see it.
3. Wizard walks the applicant through a few questions (which character, which war role interest, etc.).
4. Recruiter runs /enlist review in the ticket channel → opens an AO Master-side review form (with character search + war-role pre-assignment).
5. Recruiter clicks Approve → applicant gets the guild role on Discord + lands as a fully-set-up member on AO Master.
6. Recruiter runs /enlist done when the conversation in the ticket is done → archives the transcript into the bot's enlist archive forum + deletes the ticket channel.

If the recruiter decides to reject instead: /enlist reject @user with optional reason (the ticket closes immediately + the applicant gets a DM with the reason).

Both flows feed the same place

Whichever flow the applicant uses, they end up as the same member record. The Discord-side wizard pre-fills more (character + war role); the web-side flow leaves those for the applicant to set up after joining.

Cross-links

• Settings → Enlists — create + manage enlist links + codes.
• #Join Requests — the web review queue.
• Discord enlist flow — Discord-side deep walkthrough.
• Sign up + verify email — for applicants who don't have an AO Master account yet.