For the complete documentation index, see llms.txt. This page is also available as Markdown.

The Applications page

The dashboard review queue for reading, filtering, and acting on applications.

Sidebar → Applications opens the review queue. This page shows every submission for every application panel on your server.

The Applications page in the dashboard showing the filter row, the pending/approved/denied counts, and the table with at

You can filter the queue by status (pending, approved, denied), by date, and by reviewer, and search by a member's user ID or name. The page shows how many applications are pending, approved, and denied at a glance, so you can see your review backlog.

Click any application to open its details.

Application Details window

Shows:

  • Every answer, with the question label in bold and the member's answer below it.

  • Applicant info, including avatar, name, account creation date, and server-membership date.

  • Decision details, including the reviewer, the time, the public reason, and the internal note, if the application has been decided.

Pending applications also show Approve (green) and Deny (red) buttons.

The Application Details window, showing the answers, the applicant info, and the Approve and Deny buttons on a pending a

Approving or denying from the dashboard

Click Approve or Deny. A small pop-up opens:

  • Reason (max 1000 characters). Sent to the applicant in the DM if DM Result to Applicant is on for the option.

  • Note (max 1000 characters). Internal only. It is never sent to the applicant.

On submit, Ticket King:

  1. Records the decision on the application.

  2. Disables the buttons on the log embed and updates the status badge.

  3. On approve, grants the option's Granted Roles and removes its Roles to Remove.

  4. DMs the applicant if the option has DM Result to Applicant on.

  5. Writes an audit log entry.

Approving or denying from the log channel

The log embed in your configured log channel has Approve and Deny buttons. They behave the same as the dashboard, and clicking one opens the same decision pop-up.

To use the buttons, a reviewer needs a role listed in the application option's Reviewer Roles or the Review Applications dashboard permission. The server owner and anyone with Administrator or Manage Server can always use them. Anyone else gets an error.

Each submission keeps the Reviewer Roles that were set when it was sent. If you add a role to Reviewer Roles later, it can review new submissions but not the ones already waiting. The Review Applications permission works on every application straight away.

The application log embed in the log channel, showing its Approve and Deny buttons

Permissions to use this page

To see the page, you need the View Application History dashboard permission. The server owner and anyone with Administrator or Manage Server can also see it.

To approve or deny from this page, you also need the Review Applications dashboard permission. The same permission works for the log-channel buttons.

Applications overviewDesigning your application

Last updated

Was this helpful?