On this page
Three settings pages decide the shape of your server. One sets what each Discord role can do. One sets which role 
Hootus hands out to each kind of member. One turns whole features on and off. Set them in that order after first setup.
Permissions: who can do what
Open Settings → Permissions. This maps each Discord role to the pages and actions it can reach on the web dashboard. The server owner and any Full access role always get everything, so you never lock yourself out.
Pick a role from the Add a Discord role dropdown to add a card for it. Each card has:
- Full access. The switch at the top. On means every page, every action, every setting. Give it to people you fully trust.
- Presets. Quick buttons that set a common bundle. Admin is Full access. Officer covers recruitment, members, guild bank, analytics, and most settings. Raid Leader covers the planner, lineups, reserves, loot, and reports, plus everything Member has. Member is the baseline: view the guild, roster, raids, and group finder.
- Customize. Opens the full checklist so you can tick abilities one at a time.
The checklist is grouped:
- Pages are the website pages the role can open.
- Raids covers signups through running the night.
- Members covers member records and the people tabs.
- LFG covers moderating other members' group finder posts and applicants.
- Recruitment covers acting on applications.
- Guild Bank covers requesting from and running the bank.
- Settings covers which settings pages the role can open and change.
Hit Save when the card summary reads the way you want. If no role has Full access, Hootus warns you: admins and the owner still work, but you usually want at least one officer role marked Full access so someone besides you can manage settings.
Assigned roles: what Hootus hands out
Open Settings → Assigned roles. This is the other side of roles. Not what a role can do, but which Discord role Hootus gives someone based on their status. Each row is a member type with a dropdown. Point it at the Discord role you want, or leave it on No role assigned.
- Guild member. Verified and found in the WoW guild roster.
- Active raider. Marked as an active raider at verify.
- Guest. Has access here but is not in the WoW guild. Trusted more than a PUG, and never removed automatically.
- PUG invite. An outside player invited through a raid invite. Removed when they leave.
- Raid applicant. Someone who joined via a Discord raid signup. Removed once approved or declined. Point it at the role you want. Leave it blank and Hootus falls back to a Discord role literally named
Applicant. - Guest (old Friend slot). Friend was Guest under an older name. Point it at the same role as Guest, or leave it blank.
- Unverified. Given the moment someone joins, removed once they verify. Pick a no-permission role below the bot to gate the welcome channel. Blank keeps the welcome open.
- Officer. Read-only. Hootus reads this one to count officers on the dashboard and never hands it out. It grants no officer abilities on its own; what an officer can actually do comes from the Permissions matrix above. Leave blank if you do not track officers.
Rows save on their own a moment after you change them. Watch for the Saved tick.
Features: what is even on
Open Settings → Features. These are the master switches. Turn a feature off and its nav items and pages disappear too. Three tabs.
A few switches stay inert until their channel exists. Discord raid signups do nothing without a Raid signup channel, and PUG approval leaves signups pending until a PUG approval or officer channel is set. Wire Channels and notifications before you flip those on.
Core holds the everyday switches:
- Raids. Create and manage raids, track signups and attendance. See running a raid.
- PUG system. Invite external players via invite code, auto-removed when they leave.
- Discord raid signups. Recruited players apply in Discord and you approve them into the raid. Needs a Raid signup channel set in Channels and a Raid applicant role (or the
Applicantfallback) under Assigned roles. - PUG raid pings. PUGs who applied can opt in to a DM when you post a new raid. Needs Discord raid signups on.
- Remove PUGs who opt out. When a PUG taps No thanks right after applying, remove them from the server. Never a ranked member.
- Recruitment. Public application form and officer review queue.
- Promotions. Suggest rank promotions once members hit a tenure threshold. Set the rule in Roster and promotions.
- Member leave alerts. Posts to your log or officer channel when someone leaves, with their characters.
- Roster leaver alerts. Posts when the hourly roster sync finds characters that left the WoW guild. Off by default.
- Public welcome announcement. Posts a welcome in general each time a new member verifies.
- Flexible raids. Adds a Flex toggle for raids that have two sizes.
- Raid playlists. Adds a Single raid or Playlist choice so you can chain warm-up runs.
- Split raids. Adds a Second run time field for guilds that run the same raid twice a night.
- Soft reserves. Shows the soft reserve fields when creating a raid, and adds softres nudges to reminders.
- Bring an alt on signup. Adds a Bring an alt button so a member can name a backup character and role.
Experimental holds opt-in features still in development, plus Raid content order, where you choose which expansions show in the raid picker and in what order. Move one up to surface it first, turn one off to hide its raids, then Save order.
Legacy holds older versions kept while you migrate, like the Classic v1 planner. Turn one off to move to the current experience.
Feature switches save as you flip them.