Dashboard Overview
The Dashboard provides a user-friendly interface to manage and configure various aspects of the application.
Dashboard Structure
Section titled “Dashboard Structure”The dashboard is divided into several key sections:
User-Specific
Section titled “User-Specific”Server Management
Section titled “Server Management”Premium Management
Manage a server’s premium subscription.
Category Configuration
Configure the ticket categories.
Form Management
Create and manage forms for user input.
Custom Messages
Make beautiful customized messages.
Support Schedule
Configure a support schedule.
Analytics
View analytics of feedback and tickets.
Audit Log
View the history of actions taken.
Transcripts
Understand how transcripts work.
Global Server Settings
Section titled “Global Server Settings”There are also some global settings that affect your whole server.
| Setting | Description | Options | Default |
|---|---|---|---|
| Language | The language used for public bot messages in your server. | en, de | en |
| Manager Roles | Roles that can manage tickets, they did not claim | Server roles | None |
| Allow Manager Bypass | Whether users with a manager role are allowed to manage tickets, bypassing restrictions like claim status. | Yes/No | No |
| Out of Office Notice | A notice shown to users when they create a ticket while you’re out of office. | Status & Text | Disabled |
Localization
Section titled “Localization”There are two types of localization in the bot:
- Client-localization: This is determined by the language your Discord client is set to. It affects interactions like commands and components.
- Server-localization: This is determined by the language set in the dashboard for your server (on the overview page). It affects public messages sent by the bot (excluding custom messages).
Manager Roles
Section titled “Manager Roles”Manager roles are special roles that can manage tickets without needing to claim them first (if Allow Manager Bypass is enabled). This applies to users who have at least one of those roles. This is useful for large support hirarchies where higher level staff need to oversee tickets without being directly involved.
Those users will also be able to respond to their own close requests. This is important for when you’re testing something and create a close request in your own ticket.
Allow Manager Bypass
Section titled “Allow Manager Bypass”When this setting is enabled, users with a manager role can manage tickets without being affected by restrictions like claim status. For example, if a ticket is set to “claimed only”, a manager can still manage it even if they haven’t claimed it.
Out of Office Notice
Section titled “Out of Office Notice”The out of office notice is a message shown to users when they create a ticket while you’re marked as out of office. If enabled, users will see this notice when they open a ticket and ticket creation will be blocked until the notice it is removed again.
