Applications

Applications turn "DM an officer to join" into a structured pipeline: you define application types (Recruitment, a division, a rank), post an Apply Now button in a channel, and every submission opens a private interview channel where your reviewers read the answers, talk to the applicant, and click Approve or Deny. Approval assigns the configured role automatically.

How it fits together

• Types are created and managed in Discord with /config-appsadmin — each type has a name, description, a role to grant on approval, and optional approver/interviewer roles.
• Global settings (log channel, review channel, default roles, system on/off) also live in /config-apps settings.
• The dashboard's Applications card holds the feature toggle plus exactly one control: a checkbox to require a verified RSI citizen before anyone can submit.
• Members apply via an Apply Now button posted with /post-appadmin or by running /application directly.

Setup (admin)

1. 1

   Toggle the feature on. On the Features tab of your guild dashboard, flip the Applications card on. (Discord equivalent: /config-apps settings enable_system:True.)

2. 2

   Set the global settings. Run /config-apps settingsadmin with any of: log_channel (where submissions/approvals/denials are logged), review_channel, approved_role (default role for approved applicants), approver_role (global role that can approve any type), and interviewer_role (global role that can see interview channels). Running settings with no options shows the current configuration.

3. 3

   Create an application type. Run /config-apps createadmin — e.g. /config-apps create type:Recruitment description:Join the org role:@Recruit approver_role:@Officer interviewer_role:@Interviewer. Only type is required; per-type roles override the global ones. Use edit, delete, and toggle (activate/deactivate without deleting) to manage types later, and list to see them all.

4. 4

   Post the entry point. In Discord, run /post-app type [channel]admin — pick the type (it autocompletes) and optionally a channel (defaults to the current one). A modal lets you customize the message above the button, then the bot posts an embed with Apply Now. The embed also carries an Edit button so admins can reword it later without reposting.

5. 5

   (Optional) Require verified citizens. On the dashboard's Applications card, click Configure and check "Require verified RSI citizen to submit applications", then Save Changes. See gating below.

Applying (members)

Members can click the Apply Now button, or run /application anywhere in the server.

A few rules apply before the form opens:

• A linked citizen is required. Applicants must have run /citizen set handle:YourHandle first — the bot pulls their RSI handle into the application. If the guild also requires verified citizens, they must complete /citizen verify too.
• If multiple types are open to the member, /application shows a select menu; types whose approval role the member already holds are hidden.
• One pending application per type — a member can't stack duplicates.

The application form itself is a Discord modal with five standard questions: In-Game Name, Age, Timezone, Experience, and Motivation.

The review flow

Every submission creates a private interview space: a category named after the type and applicant, containing a text channel and a voice channel. It's visible only to the applicant, administrators, the type's approver role, and its interviewer role — perfect for a follow-up chat or a voice interview before deciding.

The bot posts the full application there, pinging the approver role (or @here if none is set), with the review buttons attached:

Only administrators and holders of the type's approver role can act on the buttons:

• Approve — the applicant receives the type's role and a congratulatory DM, the decision is posted to the log channel, the interview conversation is archived as a transcript, and the interview channels are deleted.
• Deny — a modal asks for an optional reason; the applicant is DMed the outcome (with the reason), the decision is logged, the transcript is archived, and the channels are deleted.

Members can check what's available with /appstatus — it lists the configured application types and their roles.

Requiring verified citizens

By default, applying only requires a linked RSI handle. Check "Require verified RSI citizen to submit applications" on the Applications card to additionally require full bio-token verification — members who haven't verified are told to run /citizen verify first. The gate is enforced both when clicking Apply Now and again at form submission.

Command reference

| Command | Who | Purpose | |---|---|---| | /application | Members | Apply to a configured type (requires a linked citizen) | | /appstatus | Members | List application types and their roles | | /config-apps create · edit · delete · toggle · list · settings | Admin | Manage types and global settings | | /post-app type: [channel] | Admin | Post the Apply Now entry-point embed |

Related

• Citizen Verification — the linked/verified citizen requirement explained.
• Rules Verification — a lighter-weight role gate for general server entry.
• Command reference — the full catalogue with arguments and tiers.

Have a question that isn't covered here? Ask in support.