> ## Documentation Index
> Fetch the complete documentation index at: https://bettertickets.gg/llms.txt
> Use this file to discover all available pages before exploring further.

# Commands

> The full command reference for better tickets applications: category management, applying, and reviewing, with what each command does, who can run it, and every option it takes.

## Category management

These commands create and configure application categories themselves. All require the **Administrator** or **Manage Server** Discord permission - a category's staff roles don't grant access to these, since they change configuration rather than review a single submission.

### `/application create`

Creates a new, empty application category. Run this once per category, then configure it with `/application edit` - see [Overview](/docs/applications/overview#creating-and-editing-a-category) for the full walkthrough.

<ParamField path="id" type="string" required>
  A unique identifier for the category (max 30 characters). This becomes the `category` value used in every other application command. It can't be changed later - delete and recreate the category if you need a different name.
</ParamField>

### `/application edit`

Opens the interactive settings menu for a category. See [Application settings](/docs/applications/settings) for what every page and field does.

<ParamField path="category" type="string" required>
  The category to edit. Autocompletes as you type.
</ParamField>

### `/application delete`

Permanently deletes an application category and its configuration, after a confirmation prompt. Existing submitted applications aren't deleted by this - only the category's own settings are removed.

<ParamField path="category" type="string" required>
  The category to delete.
</ParamField>

### `/application send`

Posts a category's panel - the message members click to apply - to a channel. Requires a submission channel to already be set on the category (see [Channels](/docs/applications/settings#channels)), since there'd be nowhere for a completed application to go otherwise.

<ParamField path="category" type="string" required>
  The application category to send.
</ParamField>

<ParamField path="channel" type="channel" required>
  The channel to send the panel to.
</ParamField>

### `/application stats`

Shows application statistics for a time window: how many were submitted, accepted, denied, and are still pending, optionally broken down by category or by a specific staff member's decisions.

<ParamField path="days" type="integer">
  How many days back to look. Defaults to 7.
</ParamField>

<ParamField path="category" type="string">
  Scope the stats to a single category.
</ParamField>

<ParamField path="staff" type="user">
  Scope the stats to a single staff member's decisions.
</ParamField>

## Everyday commands

### `/apply`

Applies to a category. Confirms first, then either submits immediately (if the category has no questions) or starts a DM conversation to answer them. Blocked with an explanation if you're currently ineligible - see [Who can apply again, and when](/docs/applications/overview#who-can-apply-again-and-when).

<ParamField path="category" type="string" required>
  The application category to apply to.
</ParamField>

### `/accept`

Accepts a user's submitted application - the command version of clicking the Accept button on the submission message. Requires the category's staff roles, or **Administrator**/**Manage Server**.

<ParamField path="category" type="string" required>
  The application category the submission belongs to.
</ParamField>

<ParamField path="user" type="user" required>
  The applicant to accept.
</ParamField>

<ParamField path="reason" type="string">
  The reason for accepting. Only required if the category's **Reason required on accept** setting is on (off by default).
</ParamField>

### `/deny`

Denies a user's submitted application - the command version of clicking the Deny button. Requires the category's staff roles, or **Administrator**/**Manage Server**.

<ParamField path="category" type="string" required>
  The application category the submission belongs to.
</ParamField>

<ParamField path="user" type="user" required>
  The applicant to deny.
</ParamField>

<ParamField path="reason" type="string">
  The reason for denying. Required unless the category's **Reason required on deny** setting has been turned off (on by default).
</ParamField>

<Note>
  `/accept` and `/deny` exist for when you'd rather run a command than find the submission message - both do exactly the same thing as clicking the buttons on it, including updating that message's color and footer in place.
</Note>