Skip to main content
Officers

Recruitment and applications

Open recruitment, set your needs, build the application form and apply page.

Setup & configuration6 of 8 in this track
On this page

Recruitment is where you tell prospects you're hiring, list what you need, and shape the form they fill in. You configure all of it in Settings → Recruitment. The member side, how people actually apply and how you act on their applications, lives in PUGs, recruiting, and loot.

Open or close recruitment

The first card holds two toggles.

Recruitment open. Turn this on when you want applications. When off, the public apply page shows a closed screen and stops accepting submissions. The Discord board switches to a "Recruitment closed" message.

Only accept applications from classes/specs we're recruiting. This restricts who can apply. When on, prospects can only apply as a class or spec you listed in your recruitment needs. When off, any class can apply.

These two toggles change the board wording:

  • Open, restrict off: the board reads "We're open to everyone right now." If you also have needs listed, it adds "but especially keen on:" and lists them.
  • Open, restrict on: the board leads with the open spot count, "here's who we're after:", and adds a note that applications are limited to those classes and specs.
  • Closed: the board shows "The nest is full for now. Check back soon."

Either way, while recruitment is open the board carries an Apply to join the guild button.

Guild page slug and guild description

Guild page slug. This sets your public URL. The card shows the live link (something like .../guilds/night-owls) with a copy button. Use lowercase letters, digits, and hyphens, 2 to 40 characters. Leave it empty to fall back to your guild name, or the guild ID if there's no name. Share this link anywhere off Discord. Older .../apply/... links you handed out still land in the right place.

Guild description. Scroll to the Guild description (shown on your apply page) card. Write a short blurb prospects read on your public guild page. Markdown is supported. Limit is 8,000 characters. Tell them who you are and what you're about.

Recruitment needs

The Recruitment needs card is your openings list. Hit Add need for each one. Every line has three parts:

  • Kind: Role, Class, or Spec.
  • Value: pick Tank, Healer, or DPS for a role; a class for class; or a class and spec pair for spec.
  • Count: use the minus and plus buttons to set how many you want.

Mix them freely. You can ask for 2 Healers, a whole class, and one specific spec all at once. These lines feed the board and, when the restrict toggle is on, gate who can apply.

Discord channels

Two channels, set in the recruitment card.

Recruitment channel. Where new applications land as embeds with Approve, Interview, and Reject buttons. Leave it unset to review applications only on the dashboard.

Recruitment board channel. Where the live recruitment-needs board posts and keeps itself updated in place. Leave it unset to skip the board. The board reflects your open/restrict toggles and needs list automatically.

Both channel pickers pull from your server's channels. If they fail to load, the bot may be missing View Channels permission. See Channels and notifications for wiring.

Application form

The Application questions card decides what applicants answer on top of the basics. Everyone is always asked their name, class, spec, role, and why they want to join.

Start from. Two buttons that fill the questions in for you. Nothing is remembered about which you picked, they just set the switches:

  • Community: name, class, and why they want to join. Nothing else.
  • Raiding: adds experience, availability, and an optional logs link.

The questions. Change any of them afterwards:

  • Raiding experience: what they have raided and how far they got.
  • Availability: which of your raid nights they can make. Where you have declared a schedule in the raid nights card, this asks against those nights instead of a blank box.
  • Guild history: previous guilds, and what they have killed this tier.
  • Warcraft Logs: a link to their logs, set to Don't ask, Optional, or Required.

The note field on raid signup moved to Settings → Raid automation.

Accepted realms

The Accepted realms card lists which realms a character must be on to apply. The first realm is the primary lookup target. Add every relevant shard or connected realm, especially for MoP where realms are connected. This card saves on its own as you add or remove realms. Realm lookups run on Hootus's host-level Blizzard access, not anything you configure per guild. If realms won't load, flag it to whoever runs the bot.

Save

The main cards share one Save changes bar at the bottom. It stays greyed out until you change something, and the status line tells you when your edits are saved or if a save failed. Accepted realms saves separately and does not use this bar.

Where to configure this