Application workflows that do the admin for you
Most communities run recruitment as a series of manual steps somebody has to remember: read the application, ask an officer, run an interview, hand out a role, tell the applicant. Every one of those is a place where somebody gets forgotten for a week.
Submitted
Screening
Interview
Accepted
What you get with Workflows
Guildbase turns that into a pipeline. Each stage knows who reviews it, what has to happen before it can advance, and what should fire automatically when it does — including the Discord roles that used to be handed out by whoever was awake.
Stages you define
Screening, interview, trial, accepted, denied — name them what your community calls them and order them how your process actually runs.
Actions on every stage
Add or remove Discord roles, change nicknames, send an email, fire a webhook, assign a reviewer or require an interview when an application reaches a stage.
Reversible actions
Moving an application back undoes what the stage did, so a role granted in error does not have to be chased manually.
Assigned reviewers
Route applications to a specific person or team so nothing sits in a shared queue that everyone assumes somebody else is reading.
Interview steps
Require an interview before an application can advance, with the outcome recorded against it for whoever makes the final call.
Applicant-visible status
Applicants see which stage they are at without asking, which is most of what your staff channel currently gets asked.
How it works
-
01
Lay out the stages your process actually has
-
02
Attach the actions each stage should fire
-
03
Decide who reviews at each step
-
04
Move an application and watch the rest happen
Workflows FAQs
What can a workflow stage do automatically?
A stage can add and remove Discord roles, change a nickname, send an email, call a webhook, assign a reviewer and require an interview. Several actions can run on the same stage.
What happens if I move an application back a stage?
Reversible actions are undone. A Discord role added by the stage is removed again, so correcting a mistake does not leave someone holding access they should not have.
Can different application types have different workflows?
Yes. Each application template carries its own workflow, so a staff application can run through interviews and trials while a whitelist form is a single review step.
Can I stop a reviewer accepting on their own?
Yes. Permissions decide who can advance an application to which stage, so juniors can screen and only senior staff can accept.
Do applicants get told when their status changes?
Yes. Stage changes can send Discord and email notifications, and applicants can always check status themselves from their account.
Workflows in practice
How communities in these games use it, with the application types they typically run.
FiveM applications
Whitelist, department and staff applications for FiveM roleplay servers, with Discord roles and in-game apply built in.
ER:LC applications
Department, session and staff applications for ER:LC communities, from PD and fire to civilian operations.
Arma 3 applications
Enlistment, section and specialist applications for Arma 3 milsim units, with basic training exams and rank roles.
Works with
Try Workflows on your community
Free to start, no card required. Bring your Discord server and set it up this afternoon.