Settings → Recruitment

The Recruitment tab is the one stop for everything an applicant goes through to join your guild — both Members (joining your own roster) and Allies (linked from a partner guild in your alliance). Open it from the Settings modal under ADMINISTRATION → Recruitment.

The settings here are cross-surface — they apply to both the web invite link (the page someone visits when they click your /enlist/<code> or /ally/<code> link) AND the Discord ticket button (the pinned [Enlist] or [Apply as Ally] post your bot keeps in its recruitment channels). One toggle, one set of questions, one chip — they cover both routes.

Permissions

The tab requires Approve Enlist Members. Anyone with that permission can edit the Recruitment settings on both outer tabs, create invite links, prune expired ones, and review incoming applications on #Join Requests.

Two outer tabs — Member and Ally

The tab splits in two right under the title. Pick the side you want to configure:

• Member — applicants you're recruiting into your own roster.
• Ally — applicants from partner guilds in your alliance. They keep their original home-guild membership; on your side they show up with an Ally Role chip instead of one of your regular roles.

Each outer tab carries the same shape: a Config card at the top + an Invite Links table at the bottom.

Member outer tab

Member Recruitment Config card

Top card on the Member outer tab. Two settings:

Receive new applicants (toggle) — pauses or resumes all incoming Member applications. Off pauses both the web /enlist link and the Discord [Enlist] button. Existing pending tickets keep their normal recruiter flow until closed. The Used by chips below the toggle remind you which surfaces it covers.

Custom apply questions — up to 3 free-text questions shown when an applicant clicks the Enlist button. Their answers post into the recruiter review channel right away — answers are NOT stored in the database, so they live only in the recruiter conversation. Leave a slot blank to skip it. The Required toggle beside each slot blocks submission when that slot's left empty.

Use questions to filter out low-effort applications (e.g. "Which time zone are you in?", "Link a kill from the last 7 days") or to gather quick context recruiters can act on without a back-and-forth.

Enlistment Links section

Bottom of the Member outer tab. Buttons at the top right: Prune N expired (mass-delete every expired row) and + Create Enlistment Link.

Each row shows:

• Enlister — the staff member who created the link, with avatar + display name.
• Enlistment code — the short alphanumeric handle. Shareable as https://ao-master.com/enlist/<code> via the Copy button on the right.
• Uses — how many people have joined through this link.
• Expires — relative time until the link stops working (or "Expired" with a red badge once past).
• Copy + Remove action buttons.

Creating a Member link

Click + Create Enlistment Link. The modal asks for:

• Expiry window — 1 hour / 1 day / 7 days / 30 days / never. Defaults to 7 days.
• Max uses — uncapped by default; pick a number for one-shot codes.

The new row appears at the top with a fresh code. Click Copy to copy the full URL and share it wherever recruits hang out.

What member applicants see

When someone visits /enlist/<code> they get a public-facing landing page with your guild's name, icon, your custom apply questions (if any), and a Enlist button. If they're not signed in to AO Master, they're walked through sign-up first (see Sign up + verify email).

Approval flow after they apply is on #Join Requests (same Approve Enlist Members permission). See Member enlist flow for the full walkthrough.

Ally outer tab

Ally Recruitment Config card

The Ally Config card is structured the same way as the Member one — receive toggle + Used by chips (this time covering the web /ally link + the Discord [Apply as Ally] button) + Custom apply questions — plus one Ally-only section:

Ally Role chip — the chip shown next to each ally member wherever a real role would appear (the #Allies roster list + detail, CTA Timer signup slots, Party Board signups). It is NOT a real permission role — purely a visual marker so members can tell allies apart at a glance.

• Ally Role Name — label text on the chip (default "Ally"). Pick something short that makes sense in your guild's vocabulary.
• Ally Role Color — pick a palette swatch or use the eyedropper for a custom colour. Allies see the same colour wherever their chip appears.

Ally Invite Links section

Same shape as Member Enlistment Links — list of codes with Enlister / Code / Uses / Expires / Copy + Remove action buttons, plus a + Create Ally Invite Link button at the top right.

The big difference is the public URL these codes generate: https://ao-master.com/ally/<code> instead of /enlist/<code>. Send the ally code to your alliance contact on the partner-guild side; their members visit /ally/<code> and apply as allies.

What ally applicants see

The /ally/<code> page looks like the member landing but with two differences:

• The page is labelled as an ally application (your guild's name + alliance badge).
• After applying, the applicant keeps their home-guild membership intact. On approval they appear in your #Allies channel with the Ally Role chip you configured, not in your member roster.

Approval flow is on #Join Requests, filtered to the Ally side, gated on the same Approve Enlist Members permission. The full ally application + approval walkthrough is on Members — Alliance and Discord — Ally flow.

Discord-side recruitment

If the bot is paired and the matching Discord pipeline is configured (on #Discord Integration under MANAGEMENT), applicants ALSO get a pinned button on a Discord channel that opens a ticket instead of the web link:

• Member — the [Enlist] button (or your custom label) opens a 🎯-enlist-… ticket.
• Ally — the [Apply as Ally] button opens a 🤝-ally-… ticket.

Either way, the Receive new applicants toggle, Custom apply questions, and (for ally) the Ally Role chip all apply identically. See Discord — Enlist flow and Discord — Ally flow for the Discord-side walkthroughs.

Cross-links

• Member enlist flow (web + Discord) — what happens after someone uses a Member link.
• Members — Alliance — the ally side from a member's perspective.
• #Join Requests — where staff approves / rejects both Member and Ally applications.
• Discord — Enlist flow + Discord — Ally flow — Discord-side mirrors.
• Discord Integration — pair the bot + wire up the Discord side of each pipeline.