Click "Add to Discord" and authorise Diski for your server. Make sure the Diski role sits high enough in your role list to manage the roles and channels you configure.

Log in with Discord and select a server you manage. You need the Manage Server permission (or be the owner) to configure a server.

Most pages keep your edits local until you press Save Settings. If you try to leave with unsaved changes, Diski warns you first.

Many text and embed fields accept variables like {{user.mention}} or {{guild.name}} that are replaced with live values when a message is sent. Use the variable picker on each page to insert valid ones — see the Variables Reference section.

Customise the action buttons members and staff use on a ticket — open, close, claim, and similar. For each button you can set its label text, an optional emoji, and its colour style (Primary, Secondary, Success, or Danger) so the panel matches your server's branding.

Configure the embeds and messages Diski sends for each ticket event — for example the opening message inside a new ticket, close confirmations, and other automatic notices. Edit the message type and content per event to control exactly what members and staff see.

The number of seconds the bot waits before sending the automatic opening message inside a newly created ticket. Set to 0 to send it immediately.

Controls how the bot automatically assigns a support member to each new ticket. Round Robin cycles through assignable roles evenly, Load Balanced assigns to the member with the fewest open tickets, and Disabled turns off auto-assignment.

The Discord roles whose members are eligible to be automatically assigned tickets. Members must hold at least one of these roles to be considered by the auto-assign algorithm.

When enabled, tickets that have not received a staff response within the escalation timeout will automatically trigger an escalation ping. Requires the Escalation Timeout and Escalation Role to also be configured.

How many minutes of staff inactivity must pass before an open ticket is automatically escalated. The timer resets whenever a staff member sends a message in the ticket.

The role that will be pinged in the ticket channel when escalation triggers. Choose a senior support or on-call role that should handle time-sensitive issues.

The text displayed on the Discord button. Leave blank to use the default label for that button type.

An optional emoji shown to the left of the button label in Discord. Click the field or the smiley icon to open the emoji picker.

The color style of the Discord button (Primary, Secondary, Success, or Danger). Choose a style that matches the intent of the action.

The Discord category (or channel) where newly opened ticket channels are created. All tickets start here until they are closed or archived.

The category tickets are moved into when they are closed. Requires Move Ticket on Close to be enabled.

An optional category for long-term storage of fully processed tickets after they have been closed and reviewed.

The channel used when a ticket cannot be created in the configured open category, for example because the category is full. Setting this prevents failed ticket creation.

When enabled, closing a ticket automatically moves its channel from the open category to the closed category. Disable this to leave the channel in place after closing.

When enabled, any custom permission overwrites on the ticket channel are preserved when the channel is moved to another category. Disable to inherit the destination category's default permissions.

Turns the ticket claiming system on or off for this panel. When enabled, moderators can use the Claim Ticket button to take ownership of a ticket.

When enabled, more than one moderator can claim the same ticket simultaneously. Disable this to enforce single-owner claiming.

Number of hours after which an inactive claim is automatically released so another moderator can pick it up. Set to 0 to disable auto-unclaim.

Minimum number of seconds a moderator must wait before claiming another ticket after their most recent claim. Set to 0 to remove the cooldown.

When enabled, a message is posted in the ticket channel to indicate that the ticket has been claimed or unclaimed by a moderator.

The text posted in the ticket channel when a moderator claims the ticket. Use {{moderator}} to insert the claiming moderator's mention.

Allows a claiming moderator to transfer ownership of a ticket to another eligible moderator. Disable to prevent ownership transfers.

Roles whose members are allowed to receive a ticket handoff. Leave empty to allow any support role to accept a handoff.

When enabled, members can open a ticket using a Discord slash command instead of (or in addition to) the panel button. Disable this if you only want panel-based ticket creation.

The name of the slash command members type in Discord to open a ticket (e.g. /ticket). Must be lowercase with no spaces.

Comma-separated alternative command names that also trigger ticket creation (e.g. support, yardim). Useful for multilingual servers.

How many seconds a member must wait before they can use the slash command again. Set to 0 to disable the cooldown.

When enabled, the bot's confirmation message after the slash command is only visible to the user who ran it. Disable to make the confirmation public in the channel.

The description shown in Discord's slash command picker when members browse available commands. Keep it short and clear so members understand what the command does.

Select the Discord roles whose members are treated as support staff for this panel. Users holding any of these roles will be added to every ticket channel when it opens.

The text prepended to each new ticket channel name (e.g. "ticket" produces channels like #ticket-0042). Keep it short and lowercase to stay within Discord's channel name limits.

Template for the channel name when a ticket is opened. Use {count} as a placeholder for the ticket number, for example "Ticket-{count}".

Template for the channel name after a ticket is closed. Use {count} to include the original ticket number, for example "Closed-{count}".

Sets the initial priority level assigned to every new ticket created through this panel. Moderators can override the priority on individual tickets at any time.

When enabled, the bot automatically pings all Support Roles in the ticket channel the moment a new ticket is opened, so staff are notified immediately.

When enabled, moderators must enter a reason before closing a ticket. This is useful for audit trails and ensuring consistent close notes across your team.

The display name for this ticket panel, shown to both admins and users. Choose something clear and descriptive, such as "Support", "Reports", or "Apply", so users know what kind of tickets to open here.

An optional short description of the panel's purpose. This helps you and your team distinguish between panels at a glance in the dashboard; you can always update it later from the panel's configuration page.

Toggles whether this panel is active and accepting new tickets from users. Disable a panel to pause ticket creation without deleting the panel or its history; save your changes after toggling for the update to take effect.

The maximum number of tickets a single user may have open at the same time across this panel. Once a user reaches this limit they cannot open another ticket until one of their existing tickets is closed.

The server-wide ceiling on the total number of simultaneously open tickets for this panel. When the guild limit is reached, new ticket creation is blocked regardless of per-user limits.

How long a user must wait after opening a ticket before they are allowed to open another one. Set to 0 to disable the cooldown entirely.

The maximum number of tickets a single moderator can have claimed at one time. This prevents any one staff member from being overloaded and encourages balanced ticket distribution.

The maximum number of new tickets that can be created across the entire server within a single minute. This guards against spam bursts and keeps the system responsive.

When enabled, the ticket creation button or command is automatically disabled once any configured limit (per-user or guild-wide) is reached. Disable this if you prefer to show an error message instead.

How often the per-user ticket count resets, expressed in hours. For example, setting this to 24 means a user's open-ticket counter resets every 24 hours, allowing them to open tickets again after the window passes.

Choose which ticket lifecycle message you want to edit, such as the panel embed, ticket opened/closed messages, staff notifications, or DMs sent to users. Each message type is sent at a different stage of the ticket workflow.

Edit the text and embed content that Discord will send when the selected ticket event is triggered. You can use supported variables (shown in the Variables Help section below) to insert dynamic values like the user's name or ticket channel.

Select the Discord roles whose members are treated as ticket moderators. Users with these roles gain access to staff-only actions such as force-closing, deleting, and claiming tickets.

When enabled, moderators can close a ticket immediately without waiting for the ticket owner to confirm. Useful for resolving idle or abandoned tickets.

Permits moderators to permanently delete a ticket channel rather than just closing it. Use with caution — deleted channels and their history cannot be recovered.

When enabled, the moderator who claims a ticket is mentioned in the ticket channel at the moment of claiming. Disable this if you prefer silent claim assignments.

Sets the name of the slash command moderators use to claim a ticket (e.g. "claim" produces /claim). Change this if you want a custom command name for your server.

A text template for the internal staff note attached to tickets. Supports placeholders like {{moderator}} and {{priority}} that are filled in automatically when the note is generated.

The Discord text channel where the ticket panel message (with its button or dropdown) will be posted. Members visit this channel to open a new ticket.

Controls how members interact with the panel: Single Button posts one create-ticket button, Multiple Buttons shows one button per linked ticket option, and Dropdown presents a select menu so members choose a reason before opening.

The text displayed on the primary create-ticket button (used for Single Button style and as the default label for Multiple Buttons style). Keep it short and action-oriented, for example "Open a Ticket".

An optional emoji that appears on the create-ticket button next to the label. Click the emoji picker button to browse and select any standard or server emoji.

The greyed-out hint text shown inside the dropdown select menu before a member makes a selection. Only visible when Panel Style is set to Dropdown.

Other ticket panels from this server that should appear as additional buttons or dropdown options alongside this panel's own options. Each linked panel retains its own independent settings for messages, transcripts, logging, and tickets.

When enabled, the bot will post (or keep posted) the panel message in the selected Panel Channel so members can open tickets. Disabling this hides the panel from users without deleting its configuration.

Only users who hold at least one of these roles are allowed to open a ticket on this panel. Leave empty to allow all roles.

Users who hold any of these roles are prevented from opening a ticket, even if they also hold a required role.

A comma-separated list of Discord user IDs that are explicitly banned from opening tickets on this panel regardless of their roles.

A comma-separated list of Discord user IDs that are always allowed to open tickets, bypassing role-based restrictions.

When enabled, Discord bot accounts are permitted to trigger ticket creation on this panel; disable this to restrict ticket opening to human users only.

Select the Discord roles whose members are treated as support staff for this panel. Users holding any of these roles are automatically added to every ticket channel when it opens.

The text prepended to each new ticket channel name — for example, "ticket" produces channels like #ticket-0042. Keep it short and lowercase to stay within Discord's channel name limits.

Template for the channel name when a ticket is opened. Use {count} as a placeholder for the ticket number, for example "Ticket-{count}".

Template for the channel name after a ticket is closed. Use {count} to include the original ticket number, for example "Closed-{count}".

Sets the initial priority level assigned to every new ticket opened through this panel. Moderators can override the priority on individual tickets at any time.

When enabled, the bot automatically pings all Support Roles the moment a new ticket is opened, so staff are notified immediately without needing to check manually.

When enabled, moderators must enter a reason before closing a ticket. This is useful for audit trails and ensuring consistent close notes across your team.

The Discord category (or channel) where new ticket channels are created. Placing tickets inside a category keeps your channel list organised and allows category-level permission overrides.

When a ticket is closed and "Move Ticket on Close" is enabled, the ticket channel is moved into this category. This visually separates open and closed tickets.

Optional secondary category for long-term archiving of closed tickets before they are deleted. Leave blank to skip the archive step.

If the target category is full or unavailable, the bot creates the ticket channel in this fallback channel instead. Helps prevent ticket creation failures during Discord category limits.

When enabled, the bot automatically moves the ticket channel into the Closed Category Channel when the ticket is closed. Disable to keep all channels in the same category.

When a ticket is moved to the closed category, this setting controls whether the channel's individual permission overwrites are preserved. Disable to inherit permissions from the destination category.

Number of hours of inactivity after which the bot automatically closes the ticket. Set to 0 to disable automatic closing.

How many minutes before auto-close the bot sends an inactivity warning inside the ticket. Set to 0 to skip the warning message.

The maximum number of messages allowed in a single ticket channel before it is automatically closed. Useful for keeping individual tickets focused and manageable.

When enabled, the bot automatically pins the opening ticket message inside the channel so it remains easy to find throughout the conversation.

Grants the user who opened the ticket permission to close it themselves. Disable this if you want only moderators to be able to close tickets.

Allows the ticket owner to rename their own ticket channel. Useful for panels where users provide context via the channel name, but disabling it keeps naming consistent.

When enabled, clicking Close Ticket shows a confirmation prompt before the ticket is actually closed. This prevents accidental closures.

How long (in hours) after closing that a ticket can be reopened. After this window expires the reopen button is hidden. Set to 0 to allow reopening at any time.

Roles whose members have elevated moderator permissions inside tickets, such as force-close and delete. This is separate from Support Roles, which only grants channel access.

Allows moderators to close a ticket immediately without going through the normal close confirmation flow. Useful for handling spam or abusive tickets quickly.

Grants moderators the ability to permanently delete the ticket channel after it is closed. When disabled, closed tickets can only be moved or archived.

When a moderator claims a ticket, the bot will ping them inside the ticket channel as a confirmation. Disable if you find the pings noisy.

The name of the slash command moderators type to claim a ticket (e.g. "claim" becomes /claim). Change this if the default name conflicts with another bot.

Default template for moderator audit notes appended to logs or transcripts. Use {{moderator}} and {{priority}} as placeholders that are filled in automatically.

Only users who hold at least one of these roles are allowed to open a ticket through this panel. Leave blank to allow everyone to open tickets.

Users who hold any of these roles are prevented from opening tickets through this panel, even if they also hold a required role.

A comma-separated list of Discord user IDs that are permanently blocked from opening tickets on this panel, regardless of their roles.

A comma-separated list of Discord user IDs that bypass all role restrictions and can always open tickets on this panel.

When enabled, bot accounts can trigger ticket creation through this panel. This is off by default to prevent accidental or automated ticket spam.

The Discord text channel where the panel message (with the ticket button or dropdown) is posted. Users click the button or choose from the dropdown in this channel to open a ticket.

Controls how ticket creation is presented to users: a single button, multiple buttons (one per ticket option), or a dropdown select menu. Multiple Buttons and Dropdown require ticket options to be configured.

The text shown on the primary ticket creation button when Panel Style is set to Single Button. Keep it concise, for example "Open a Ticket" or "Get Support".

An optional emoji displayed on the left side of the primary ticket creation button. Click the emoji picker to choose a Unicode or custom server emoji.

The greyed-out hint text shown inside the dropdown select menu before a user makes a selection. For example, "Select ticket reason" or "Choose a department".

Other ticket panels to merge into this panel message when using Multiple Buttons or Dropdown style. Each linked panel keeps its own independent settings and ticket channels.

Toggles whether the panel message is actively shown in the panel channel. Disabling hides the ticket button from users without deleting any settings.

The bold title line shown at the top of the panel embed message. Keep it short and inviting, for example "Need Help?" or "Support Center".

The main body text of the panel embed, shown below the title. Use this to explain what the ticket system is for and how users should use it.

Small text shown at the bottom of the panel embed, typically used for branding like "Powered by Diski" or a support team name.

A URL to an image displayed as a small thumbnail in the top-right corner of the panel embed. Leave blank for no thumbnail.

A URL to a full-width image displayed below the embed description. Useful for a banner or visual header. Leave blank for no image.

When enabled, Discord displays the current date and time in the embed footer area. Useful for showing when the panel was last updated.

When enabled, users can open a ticket by typing the configured slash command in any channel instead of using the panel button or dropdown.

The name of the slash command users type to open a ticket (e.g. "ticket" becomes /ticket). Must be lowercase with no spaces.

Additional command names that also trigger ticket creation, separated by commas (e.g. "support, yardim"). Useful for multilingual servers.

How long a user must wait between uses of the ticket slash command. This prevents rapid repeated ticket creation via the command.

When enabled, the bot's confirmation response after the slash command is only visible to the user who ran it. Keeps the channel tidy by hiding bot responses from others.

The description shown in Discord's slash command autocomplete list when users type the ticket command. Helps users understand what the command does before they run it.

When enabled, tickets are created as Discord threads rather than dedicated channels. This is useful on servers that want to keep ticket conversations inside a single channel.

How long an inactive thread stays visible before Discord automatically archives it. Options range from 1 hour to 7 days.

Adds a slowmode delay (in seconds) to ticket threads, limiting how often any individual user can send messages. Set to 0 to disable slowmode.

When enabled, ticket threads are created as private threads that are only visible to invited participants. Requires the server to have Community features enabled.

Template for the thread name when a ticket thread is created. Use {{user}} to insert the ticket opener's username, for example "ticket-{{user}}".

The first message posted inside a new ticket thread to greet the user. Use {{user}} and {{moderator}} as placeholders.

The channel where the bot posts saved ticket transcripts. A transcript file or link is sent here each time a transcript is triggered.

When enabled, the bot sends the transcript directly to the ticket owner's DMs in addition to (or instead of) posting it in the transcript channel.

Controls when the DM transcript is sent to the user: when the ticket is closed, when it is deleted, or both.

When enabled, the bot automatically generates and saves a transcript without requiring anyone to manually press the transcript button.

Controls which event triggers the automatic transcript save: when the ticket is closed, when it is deleted, or both.

When enabled, file attachments from the ticket conversation are included in or linked from the saved transcript. Disable to keep transcripts text-only.

When enabled, the bot scans transcript content and redacts patterns that look like tokens, API keys, or passwords before saving. Recommended to keep enabled.

When enabled, the transcript message posted to your transcript channel includes the built-in details embed (owner, ticket name, status, participants, close reason, timestamps). Disable this to let your own editable Transcript message fully control how that message looks — the transcript file and Direct Link button are always kept either way.

The channel where ticket event log messages are posted. All selected log events will appear in this channel as embed messages.

Select which ticket lifecycle events the bot should post to the log channel. You can enable any combination of ticket created, claimed, closed, reopened, deleted, and transcript saved.

When enabled, any moderator notes added to the ticket are included in the log embed. Useful for keeping an audit trail of staff actions.

When enabled, a link to the saved transcript is appended to the log embed for events that produce a transcript. Requires a transcript channel to be configured.

When enabled, the bot mentions the Critical Ping Role inside the log channel whenever a ticket meets or exceeds the critical priority threshold.

The role that is mentioned in the log channel when a high-priority ticket event is logged. Only used when Ping Role on Critical Events is enabled.

The minimum priority level that triggers the critical role ping. For example, selecting High will ping the role for both High and Urgent tickets.

How many seconds after a ticket is opened before the bot sends its automatic response or assignment message. A short delay (e.g. 5 seconds) gives the user time to read the welcome message first.

Controls how the bot distributes tickets among available staff: Disabled turns off auto-assignment, Round Robin cycles evenly through assignable roles, and Load Balanced assigns to whoever has the fewest open tickets.

The roles whose members are eligible for automatic ticket assignment. The bot picks from members of these roles according to the selected Auto Assign Mode.

When enabled, tickets that remain unclaimed or unresponded to past the escalation timeout are escalated by pinging the Escalation Role.

How many minutes of no response must pass before the bot escalates the ticket by pinging the escalation role. Only applies when Enable Escalation is on.

The role that is pinged inside the ticket channel when the escalation timeout is reached. Typically a senior support role or team lead.

The maximum number of simultaneously open tickets a single user can have on this panel. Once reached, the user is blocked from opening more until one is closed.

The server-wide cap on total open tickets for this panel at any one time. Useful for preventing support overload during busy periods.

How long a user must wait after closing a ticket before they can open a new one. Set to 0 to disable the cooldown.

The maximum number of tickets a single moderator can claim at the same time. Helps distribute workload evenly across your support team.

The maximum number of tickets that can be opened across the whole server within a single minute. Protects against sudden bursts of ticket creation.

When enabled, the ticket creation button or dropdown is temporarily locked for all users once the guild-wide open ticket limit is reached.

How often (in hours) per-user and guild-wide ticket counters are reset. This determines how long a user must wait before their ticket count is cleared.

Turns on the ticket claiming system so moderators can assign themselves as the owner of a ticket. When disabled, the Claim Ticket button is hidden.

When enabled, more than one moderator can claim the same ticket simultaneously. Useful for complex tickets that need collaboration.

Number of hours after which an inactive claimed ticket is automatically unclaimed, making it available for another moderator to pick up. Set to 0 to disable.

How long a moderator must wait between claiming tickets. Prevents rapid claim-switching and ensures deliberate assignment.

When enabled, the bot posts a message inside the ticket channel whenever it is claimed or unclaimed, making the current ownership visible to everyone in the ticket.

The message posted inside a ticket when a moderator claims it. Use {{moderator}} as a placeholder for the moderator's name.

When enabled, moderators can transfer their claim on a ticket to another eligible moderator. The Handoff Roles list controls who is a valid handoff target.

The roles whose members can receive a ticket handoff from the current claiming moderator. Leave blank to allow handoffs to any moderator role.

The text label shown on the button or in the dropdown for this ticket option. Keep it short and descriptive, for example "Billing Support" or "Technical Issue".

An optional emoji displayed alongside this ticket option's label in the button or dropdown. Click the emoji picker to choose a Unicode or custom server emoji.

The colour style of the button for this ticket option when Panel Style is set to Multiple Buttons. Choose from Primary (blue), Secondary (grey), Success (green), or Danger (red).

Overrides the panel's default Open Category for tickets opened through this specific option. Leave blank to use the panel default.

Overrides the panel's default Support Roles for tickets opened through this specific option. Leave blank to use the panel default roles.

A short description shown in the dropdown or used as internal context for this ticket option. In dropdown mode it appears as the sub-text beneath the option label.

The Discord text channel where transcript files are posted when a ticket is closed or deleted. Leave unset if you only want transcripts sent via DM or not stored in a channel.

When enabled, the bot will send the ticket transcript directly to the ticket owner's DMs in addition to (or instead of) posting it in the transcript channel.

Controls when the DM transcript is sent: when the ticket is closed, when it is deleted, or both. This only applies when Send Transcript to User DM is enabled.

When enabled, the bot automatically generates and saves a transcript without requiring a staff member to manually trigger it.

Determines the event that triggers an automatic transcript save: when the ticket is closed, when it is deleted, or both. Only takes effect when Auto Save Transcript is enabled.

When enabled, files and images uploaded inside the ticket are included or linked in the saved transcript so nothing is lost after the channel is removed.

When enabled, the bot scans message content for patterns that look like API keys, tokens, or passwords before saving the transcript and replaces them with redacted placeholders.

When enabled, the transcript message posted to your transcript channel includes the built-in details embed (owner, ticket name, status, participants, close reason, timestamps). Disable this to let your own editable Transcript message fully control how that message looks — the transcript file and Direct Link button are always kept either way.

Controls the Discord channel permission overwrites applied when a new ticket channel is created, for three audiences: the Ticket Opener, your Support Team roles, and Everyone else in the server. For each permission you can set Allow, Deny, or Neutral (inherit) — Neutral means the permission is left untouched so the member's existing role permissions decide. By default the opener and support team can view and chat in the ticket while Everyone is denied View Channel so tickets stay private. For safety, Everyone can never be allowed to View Channel: the bot always forces that permission to Deny so a misconfiguration cannot expose tickets to the whole server. The bot's own access and any blocked roles are always applied automatically and are not configurable here.

The buttons or dropdown options your panel offers — for example General Support, Billing, or Report a player. Each type can override the category its tickets open under, add extra support roles on top of your team roles, use its own channel naming and welcome message, and ask up to 5 intake questions before the ticket opens. Fields left unset inherit the panel-wide value shown next to them.

How members pick a topic on the panel message. Buttons shows one button per enabled type (in rows of five, up to 25); Dropdown shows a single select menu with one option per type. Dropdown is usually cleaner when you offer more than three types — it's one switch, so you can change it any time.

The roles that handle tickets. Members with any support role can see every ticket this panel opens and can claim, close, and manage them. When "mention team on open" is on, these roles are pinged inside each new ticket. Individual types can add extra roles on top of these.

A senior tier above support. Managers can do everything support can, plus force-close, reopen, or delete any ticket — including from the dashboard — and release tickets claimed by someone else.

Lets a staff member take ownership of a ticket with the Claim button so everyone can see who is handling it. Optionally restrict replies to the claimer — other staff keep read access but only the claimer (and managers) can respond. Restrict-to-claimer can't be combined with round-robin auto-assign.

The Discord category new ticket channels are created under. Set the default in the Behavior tab; individual types can override it (an "Overridden by N types" chip appears when they do). Discord categories hold at most 50 channels — if the category is full, the ticket is still created without one and a warning is posted to your log channel.

Templates for the ticket channel's name while open and after close — for example ticket-{ticket.number} becomes #ticket-0042. Short aliases {number}, {user}, {type}, and {panel} also work here, and names are slugified to fit Discord's rules. Note: Discord only allows 2 renames per channel per 10 minutes, so the rename on close can lag behind.

What happens to the channel after close: Keep leaves it where it is (the default), Move sends it to a Closed category you pick, and Auto-delete removes the channel after the delay you set (the transcript is saved first, and the ticket's history stays in your dashboard Inbox). If the delete delay is shorter than your reopen window you'll see a warning — tickets could be deleted while still reopenable.

Allows a closed ticket to be reopened with everything restored — channel access, name, and category. The window sets how many hours after close a ticket stays reopenable; 0 means no time limit. Staff can always reopen within the window; the opener can too if opener-close is allowed.

Staff can ask the opener "this looks resolved — accept to close?" using /ticket closerequest. The opener can accept (which closes the ticket) or keep it open. If they don't respond, the ticket auto-closes after the number of hours set here; 0 means close requests never auto-close.

Hands-off housekeeping, off by default. Inactivity: after the warn threshold with no messages, Autopilot posts a warning in the ticket; after the close threshold it closes the ticket automatically. Escalation: when a ticket sits unclaimed for too long, Autopilot pings the escalation role you choose — once per ticket.

When a ticket closes (or on demand), Diski saves a full HTML transcript. It can be posted to a channel, DMed to the opener with a permanent link that never expires, and viewed in the dashboard Inbox. Redaction scrubs anything that looks like tokens, API keys, or passwords. If no transcript or log channel is set, the Discord post is skipped — the dashboard copy and DM link still work, and the panel shows a warning badge so you know.

Pick a log channel and choose which ticket events to record — opened, claimed, unclaimed, closed, reopened, deleted, transcript saved, and close requested. Each event posts a compact embed to the log channel. Transcripts post to their own channel if you set one; otherwise they fall back to this log channel.

Fine-grained channel permissions applied to every new ticket, for three audiences: the Ticket Opener, Support & managers (your team roles plus any type-specific roles), and Everyone. Each permission can be Allow, Deny, or Neutral (inherit). For safety, Everyone can never be allowed View Channel — Diski forces it to Deny so a misconfiguration can't expose tickets to the whole server. The bot's own access and blocked roles are applied automatically.

Per-panel guardrails. Max open tickets per member caps how many tickets one person can have open on this panel at the same time (0 = unlimited). Cooldown makes members wait between opening tickets on this panel. Both apply to this panel only — a ticket on another panel never counts against them. For blocking someone from every panel at once, use /tickets blacklist in Discord.

The internal name for this application form, shown in the dashboard and used to identify the form in panels and the review queue. Choose a short, descriptive name that clearly indicates the purpose of the form.

An optional description of the application form that provides context for reviewers and admins. This text is visible in the dashboard and can be used to note the intended audience or any special requirements.

The maximum number of pending (unanswered) applications a single user may have open at the same time for this form. Set to 1 to prevent duplicate submissions while one is still under review.

How long (in minutes) a user must wait before they can resubmit this form after their previous submission was decided. Set to 0 to allow immediate resubmission.

The Discord channel where completed application submissions are posted for reviewers to see and act on. This channel should be restricted to staff or reviewers.

An optional channel where a full transcript of each application (all questions and answers) is sent upon submission. Useful for archiving or auditing completed applications.

Roles whose members are permitted to approve or deny submissions for this form. Members with any of these roles will see review action buttons on application posts in the destination channel.

Roles that a user must have in order to submit this form. If a user lacks all of the required roles, the bot will inform them and prevent submission.

Roles that disqualify a user from submitting this form. Any user holding at least one blocked role will be prevented from applying, regardless of other role requirements.

Toggles whether this form is active and available for users to submit. Disabled forms are hidden from all panels and cannot be submitted until re-enabled.

Selects which application form you are currently editing questions for. All question changes apply only to the selected form.

Marks this question as mandatory so users cannot submit the form without providing an answer. Toggle the checkmark icon to enable or disable the required flag for each question.

The question text shown to the user when they are filling out the application. Keep labels clear and concise so applicants know exactly what information to provide.

Determines the input style for this question: Short Text (single line), Paragraph (multi-line), or Multiple Choice (predefined options the user picks from). Changing the type resets length constraints and choice options.

Greyed-out hint text shown inside the answer input before the user types anything. Use this to give an example answer or clarify the expected format.

The minimum number of characters a user must enter for this question. Set to 0 to allow any-length answers (only applies to text input types).

The maximum number of characters allowed for this question's answer, up to 2000. Use this to keep responses concise and prevent excessively long submissions.

A display name for this application panel, used to identify it in the dashboard. The name is not shown to Discord users — it is for your own organizational reference.

The Discord channel where the panel message (with the Apply button or dropdown) will be sent or updated. Users go to this channel to start their application.

Controls how the apply interaction appears on the panel message. Single Button shows one button for all forms, Form Buttons shows one button per form, and Dropdown shows a select menu listing all assigned forms.

Selects which application forms are accessible from this panel. Only enabled forms appear for users; if no forms are selected, all enabled forms for this server are shown.

The text displayed on the single apply button when the panel style is set to Single Button. Defaults to 'Apply Now' if left blank.

An optional emoji displayed alongside the button label or as a dropdown option icon. Click the emoji picker icon to choose one from the full emoji library.

The default text shown in the dropdown select menu before a user makes a selection. Displayed only when the panel style is set to Dropdown.

A channel where the bot posts a log entry each time an application is approved or denied. This provides an auditable trail of all review decisions.

When enabled, the bot automatically creates a Discord thread on each application post in the destination channel, giving reviewers a dedicated space to discuss the submission before deciding.

When enabled, the bot sends a direct message to the applicant as soon as their application is approved or denied, using the Accepted or Denied Message templates you configure below.

The message sent to the applicant (via DM or channel, depending on settings) when their application is approved. Supports template variables such as {{user}}, {{reviewer}}, and {{applicationName}}.

The message sent to the applicant when their application is denied. You can include {{reason}} to show the reviewer's stated reason for rejection if one was provided.

The first message displayed to the user when they trigger an application from the panel, before they begin answering questions. Use it to set expectations or provide instructions.

The message sent to the user after they have successfully submitted all answers and the application is received. Use it to thank the applicant and tell them what to expect next.

Filters the review queue by searching across applicant username, form name, and the submission summary. The search updates results automatically after a short delay as you type.

Narrows the review queue to show only submissions with a specific status: All, Pending, Approved, or Denied. Combine with the search field to find specific submissions quickly.

Controls how many application submissions are shown per page in the review queue. Increase this number to review more submissions at once without paginating.

Turns the Member Verification module on or off. When enabled, the bot will post (or update) a verification panel in your chosen channel and begin gating the verified role.

The text channel where the bot will post the verification panel embed. New members should be able to see this channel but not the rest of the server until they verify.

The role assigned to a member as soon as they pass the verification challenge. This role should unlock the rest of your server's channels.

An optional role that is removed from a member once they successfully verify. Use this as a gate role to restrict unverified members to only the verification channel.

An optional text channel where the bot will send a message for every successful or failed verification attempt, useful for moderation auditing.

Determines the challenge a member must complete to get verified. Button is the simplest (one click), Code and Math open a modal requiring a typed answer to resist bots, and Reaction asks the member to react to the panel message.

The title displayed at the top of the verification embed in the verification channel. Keep it short and clear so members immediately understand what they need to do.

The text shown on the verification button or action. This setting has no effect when the Reaction method is selected.

The accent color of the verification panel embed, entered as a hex code (e.g. #5865F2). Use your server's brand color or a color that stands out in the channel.

The body text of the verification embed shown to members. Use this to explain your rules or simply instruct members to click the button to gain access.

When enabled, the bot will kick a member from the server after they exceed the configured maximum number of failed attempts. Only applies to the Code and Math verification methods.

The number of failed verification attempts a member is allowed before being kicked. Set to 0 to allow unlimited attempts (the member will never be kicked).

The Twitch username of the streamer you want to monitor (e.g. "shroud" or "pokimane"). Enter the exact username as it appears in the Twitch channel URL.

The Discord text channel where the live alert message will be posted when the streamer goes live. Only text channels are available for selection.

One or more Discord roles that will be mentioned in the alert message when the stream starts. Leave empty to send the notification without any role pings.

The content of the notification posted to Discord when the streamer goes live, supporting plain text and rich embeds with dynamic Twitch variables such as {{streamer.name}} and {{streamer.title}}. Use the embed builder to customize colors, descriptions, and footers.

A comma-separated list of game names; if set, alerts are only sent when the streamer is playing one of the listed games. Leave this field empty to receive alerts regardless of which game is being played.

A comma-separated list of keywords; if set, alerts are only sent when the stream title contains at least one of the listed keywords. Leave empty to receive alerts for any stream title.

When enabled, the live notification message is automatically deleted from Discord once the streamer goes offline. This keeps your channel tidy without requiring manual cleanup.

The Kick channel slug is the unique identifier that appears in the streamer's URL after kick.com/ (for example, the slug for kick.com/xqc is "xqc"). Enter it exactly as it appears in the URL, without any slashes.

The Discord text channel where the go-live alert will be posted when this streamer starts broadcasting. Only text channels your bot has permission to send messages in are shown.

One or more Discord roles to @mention in the notification message so members with those roles are pinged when the stream goes live. Leave empty to send the alert without any role mentions.

The message sent to the notification channel when the streamer goes live, supporting plain text and one or more Discord embeds. You can use Kick template variables (such as {{streamer.name}} and {{streamer.title}}) to insert live stream details automatically.

The unique identifier for the YouTube channel you want to monitor, in the format UCxxxxxxxxxxxxxxxxxxxxxx. You can find it in the channel URL on YouTube or via third-party tools like commentpicker.com/youtube-channel-id.php.

The Discord text channel where the bot will post the alert message when the subscribed YouTube channel goes live. Only text channels your bot has permission to send messages in will appear in the list.

One or more Discord roles to @mention in the notification message so those members are pinged when the stream starts. Leave this empty if you do not want to ping any roles.

The message the bot sends when a live stream is detected — you can use plain text, an embed, or both, and insert dynamic variables such as {{streamer.name}} or {{streamer.title}} to include real-time stream details.

The TikTok handle of the creator you want to monitor, entered without the leading @ symbol. Diski will track this account and trigger a notification whenever they start a live stream.

The Discord text channel where the live alert message will be posted when the creator goes live. Only text channels your bot has permission to send messages in will appear in this list.

One or more Discord roles that will be @mentioned in the notification message so members with those roles are pinged when the stream starts. Leave empty to send the alert without any role mentions.

The content of the Discord message sent when the creator goes live, supporting both plain text and rich embeds with dynamic variables like {{streamer.name}} and {{streamer.title}}. Use the embed builder to customise colours, descriptions, and footers to match your server's style.

A display label for this embed sender used only inside the dashboard to help you identify it. It does not appear in the Discord message that gets sent.

The Discord text channel where this embed will be posted when you click Send. Only text channels your bot has access to are listed.

The full message payload to send, including optional plain-text content and one or more rich Discord embeds. Use the embed builder to set titles, descriptions, colours, thumbnails, and footers.

Switch between Embed mode (a rich card with colour, title, image, and footer fields) and Text mode (a plain message with markdown support). Each embed configuration can only be one type at a time.

Small text shown above the embed title, typically used for the source or author attribution. Supports Discord template variables.

A direct URL to an image displayed as a small circular icon beside the Author Name. Must be a publicly accessible HTTPS image URL.

Makes the Author Name a clickable hyperlink when provided. Must be a valid HTTPS URL.

The bold headline of the embed, displayed prominently at the top of the card. Supports Discord template variables.

A direct URL to a small image shown in the top-right corner of the embed. Must be a publicly accessible HTTPS image URL.

When set, the embed Title becomes a clickable hyperlink pointing to this URL. Must be a valid HTTPS URL.

The main body text of the embed. Supports full Discord markdown (bold, italics, code blocks, bullet lists) and template variables.

Small text shown at the bottom of the embed, often used for disclaimers, credits, or contextual notes. Supports template variables.

A direct URL to a tiny circular image displayed beside the Footer Text. Must be a publicly accessible HTTPS image URL.

The colour of the left accent stripe on the embed card. Click the colour swatch to open the colour picker and choose any hex colour.

When checked, the current date and time is appended to the embed footer at the moment the message is sent. Useful for audit logs and timed announcements.

Select the Discord text channel where the bot will maintain a persistent (sticky) message. Only one persistent message is allowed per channel, so channels already in use by another entry are excluded from the list.

Toggle this on to make the persistent message active in the selected channel. When disabled, the bot stops reposting the message but the configuration is preserved so you can re-enable it later.

The word or phrase the bot watches for in messages. When a message matches this text (according to the Match Type), the bot will send the configured response.

Controls how the trigger text is compared against incoming messages. Choose Contains to match anywhere in the message, Exact to require the entire message to equal the trigger, Starts With to match only at the beginning, or Regular Expression for advanced pattern matching.

Restricts which channels this responder is active in. Leave empty to allow the responder to fire in all text channels the bot can read.

The minimum number of seconds that must pass before this responder can fire again in the same channel. Set to 0 to disable the cooldown and allow the bot to respond every time the trigger is matched.

Toggles this responder on or off without deleting it. When disabled, the bot will ignore matching messages and send no response.

A friendly label for this scheduled message used only inside the dashboard. Choose something descriptive so you can easily identify it in your list of automations.

The Discord text channel where the scheduled message will be posted. Only text channels in your server are available for selection.

The exact date and time when a one-time scheduled message should be sent. The time is interpreted in the Timezone you select below.

The timezone used to interpret the Run At datetime. Select the timezone that matches your intended send time so the message fires at the correct local time.

How often a recurring message repeats — every hour, every day, every week, or a fully custom cron schedule. Your choice here determines which additional options appear below.

For weekly recurring messages, the day of the week on which the message will be sent. Combined with Time of day to form the exact send time.

The time (hours and minutes) at which a daily or weekly recurring message is sent. Interpreted in the Timezone selected below.

For hourly recurring messages, the minute within each hour when the message fires (0–59). For example, setting 30 sends the message at :30 past every hour.

A raw cron expression in standard 5-field format (minute hour day month weekday) for advanced scheduling needs. Use this when the preset frequencies do not cover your use case.

The timezone used when evaluating the recurring cron schedule. Ensure this matches the timezone of your intended audience so messages arrive at the expected local time.

Toggle whether this scheduled message is active. Disabled messages are saved but will not fire until re-enabled.

A keyword responder watches every message in your server (or specific channels) and automatically replies when the message text matches a trigger you define. You can choose how the trigger is matched (contains, exact, starts with, or regex), restrict it to particular channels, and set a per-trigger cooldown to prevent spam.

A scheduled message tells the bot to post a specific message to a chosen channel either once at a set date and time, or on a repeating schedule (hourly, daily, weekly, or a custom cron expression). Use this for recurring announcements, reminders, or any content that should appear on a predictable cadence.

A persistent (sticky) message is automatically reposted to the bottom of its channel every time other members send messages, keeping it always visible as the latest message. Only one persistent message is allowed per channel, and the bot throttles reposts to avoid hitting Discord rate limits.

Toggles whether the bot sends a message when a new member joins the server. Turn this on to activate the welcome channel and message settings below.

The text channel where the welcome message will be posted whenever someone joins. Only text channels are shown in the dropdown.

The message the bot sends when a member joins — compose it as plain text, a rich embed, or both. You can use template variables (e.g. {user.mention}) to personalize the message for each new member.

Toggles whether the bot sends a message when a member leaves or is removed from the server. Turn this on to activate the goodbye channel and message settings below.

The text channel where the goodbye message will be posted whenever someone leaves. Only text channels are shown in the dropdown.

The message the bot sends when a member leaves — compose it as plain text, a rich embed, or both. Template variables such as {user.tag} let you include the departing member's information.

Toggles whether this reaction role is active in your server. When disabled, the bot will not process role assignments from this configuration even if the message exists in the channel.

A display name for this reaction role configuration used only inside the dashboard to help you identify it. It does not appear in the Discord message sent to members.

The text channel where the bot will post (or has posted) the reaction role message. Members must be able to see this channel to interact with the role picker.

Controls how members pick roles: Emoji uses message reactions, Button adds clickable Discord buttons to the message, and Dropdown presents a select menu. Each type has its own set of options configured below.

The text and/or embed that the bot sends to the channel as the reaction role message. You can write plain text, build a rich embed, or combine both — this is what members will see when choosing roles.

The individual emoji reactions, buttons, or dropdown entries that members click to receive a role. Each option maps one interaction choice to one or more Discord roles that will be granted or removed.

Turns on automatic role assignment for new members the moment they join your server. When disabled, no roles are granted on join regardless of other settings.

The roles that will be given to every new member who joins the server. You can select multiple roles; all of them will be assigned at once (after any configured delay).

How many seconds to wait after a user joins before assigning the auto roles. Set to 0 to assign immediately; use a delay if you want to allow verification flows to complete first.

Activates automatic role removal after a configurable delay. Useful for timed trial roles, event passes, or cooldown roles that should not persist indefinitely.

The roles that will be automatically stripped from members once the remove delay has elapsed. Select all roles you want to treat as temporary.

How many seconds after a member receives a temporary role before it is automatically removed. The timer starts when the role is first assigned.

Activates rule-based role chaining so that granting one role can automatically grant another. Each rule is configured independently with its own trigger, target, and optional delay.

The role a member must receive to activate this rule. When any member is assigned this role, the bot will queue assignment of the linked role.

The role that will be granted to the member after the trigger role is detected. This is the downstream role in a linked-role rule.

How many seconds to wait after the trigger role is assigned before granting the linked role. Set to 0 to assign the linked role immediately.

The name or description of the item being given away, displayed as the title of the giveaway message. Keep it short and descriptive so members immediately know what they can win.

An optional longer description shown below the prize title in the giveaway message. Use this to add context, instructions, or sponsor information.

The text channel where the giveaway message will be posted and where members react to enter. Choose a channel your members can see and access.

An optional separate channel where the winner announcement is posted when the giveaway ends. If left empty, the announcement is sent in the same channel as the giveaway.

The number of winners to be randomly selected when the giveaway ends. Set to 1 for a single winner or higher to award multiple members at once.

How long the giveaway runs before winners are drawn, specified in hours. The minimum is 1 hour and the maximum is 168 hours (7 days).

Only members who hold at least one of the selected roles are eligible to enter. Leave this empty to allow all members to participate.

Members with any of these roles can enter the giveaway regardless of other eligibility restrictions such as required roles or minimum account age.

The maximum number of entries accepted before the giveaway closes early. Leave this field empty to allow unlimited participants.

The minimum age of a Discord account in days required to enter. Set to 0 to allow accounts of any age, or use a higher value to reduce bot or alt-account entries.

An optional custom embed or text message that overrides the default giveaway announcement format. Use this to match your server's branding or add extra details; template variables are supported.

When enabled, each individual event type can be routed to its own dedicated Discord channel, letting you separate logs by category. When disabled, all enabled events are sent to a single shared log channel.

Select any text channels whose activity you want to exclude from logging. Events originating in these channels — such as message edits or deletes — will be silently skipped.

Select roles whose members' actions will not be logged. Useful for exempting bots, staff, or other trusted groups from appearing in your audit logs.

The single Discord channel where all enabled event logs will be posted when Channel Specific Logging is turned off. Pick a private staff or mod channel to keep logs out of public view.

Toggles for logging message-related activity, including deleted messages, edited messages, and bulk message deletions. Enable the events you want and optionally assign each a dedicated channel when Channel Specific Logging is on.

Toggles for logging member-related activity such as joins, leaves, bans, unbans, timeouts, nickname changes, and role assignments or removals. Enable individual events to track your server's membership changes.

Toggles for logging role-related changes in your server, covering role creation, deletion, and updates. Enable these to maintain an audit trail of permission and role structure changes.

Toggles for logging Discord channel lifecycle events — when channels are created, deleted, or updated. Useful for tracking server structure changes made by admins or bots.

Toggles for logging changes to your server's custom emojis, including when emojis are created, deleted, or updated. Enable these to keep track of who is managing your emoji library.

Toggles for logging voice channel activity, specifically when members join or leave a voice channel. Enable these to monitor voice usage patterns or investigate incidents in voice channels.

Master switch that activates or deactivates all Guild Linker rules for this server. When disabled, no automatic role syncing will occur regardless of your configured rules.

The external Discord server that should receive the synced role. Only servers where the bot is added and you have Manage Server or Administrator permissions are shown.

The role on this server that triggers the sync. When a member receives this role, the bot will automatically assign the Target Role in the Target Server.

The role to assign in the Target Server when the rule fires. Select the Target Server first so this dropdown can load that server's available roles.

How many seconds to wait after the source role is assigned before granting the target role. A value of 0 means the sync happens immediately; use a delay if you need to allow time for other automations to run first.

Toggle between Monthly and Yearly billing. Choosing Yearly saves 15% compared to the monthly rate, and the discounted price is reflected immediately in each plan card.

When toggled on, Diski will operate in this server through your connected bot instead of the default Diski bot. Requires a valid bot token to be saved first; toggling on without a stored token will prompt you to supply one.

Paste the secret token from your Discord Developer Portal bot page here to connect your custom bot to Diski. The token is stored securely and never displayed again — leave the field blank on future saves to keep the existing token unchanged.

Write variables with double curly braces like {{guild.name}}. Single-brace or unknown variables are rejected on save; use the variable picker shown on each page to insert valid ones.

{{user.mention}}, {{user.username}}, {{user.displayName}}, {{user.id}}, {{user.tag}}, {{user.avatarUrl}} — refer to the user who triggered the action.

{{member.mention}}, {{member.displayName}}, {{member.nickname}}, {{member.roles}}, {{member.roles.count}}, {{member.joinedAt}} — the server-member view of a user.

{{guild.name}}, {{guild.id}}, {{guild.iconUrl}}, {{guild.memberCount}}, {{guild.ownerId}}, {{guild.createdAt}} — details about the server.

{{channel.mention}}, {{channel.name}}, {{channel.id}} — the channel involved in the message.

{{streamer.name}}, {{streamer.username}}, {{streamer.title}}, {{streamer.game}}, {{streamer.url}}, {{streamer.profileImage}} — available in Twitch, Kick, YouTube and TikTok notifications.

{{giveaway.prize}}, {{giveaway.description}}, {{giveaway.winnerCount}}, {{giveaway.channel}}, {{giveaway.endDate}}, {{giveaway.endRelative}}, {{giveaway.image}}, {{giveaway.status}} — available in giveaway messages.

The master switch for the module. When off, members cannot submit suggestions and the sticky submit panel is removed from the channel. Turn it on and choose a suggestion channel to start collecting ideas.

The channel where submitted suggestions are posted as embeds with upvote and downvote buttons. This field is required while the module is enabled — members submit through the modal and their suggestion appears here for voting.

An optional channel where a summary embed is posted whenever a suggestion is approved. Leave it empty to skip announcing approvals in a separate channel.

An optional channel where a summary embed is posted whenever a suggestion is denied. Leave it empty to skip announcing denials in a separate channel.

An optional private channel where Diski posts a one-line log entry for every approve or deny decision, including who made it. Useful for keeping a staff audit trail.

Roles whose members are allowed to approve or deny suggestions using the staff buttons on each post. Members with the Manage Server permission can always approve or deny regardless of these roles.

When enabled, every suggestion must be manually approved or denied by a staff member and the automatic vote thresholds are ignored. Turn this off to let Diski auto-decide suggestions based on their vote score.

Automatically approves a suggestion once its net score (upvotes minus downvotes) reaches this number. Set to 0 to disable auto-approval. Ignored while Require Staff Confirmation is on.

Automatically denies a suggestion once its net negative score (downvotes minus upvotes) reaches this number. Set to 0 to disable auto-denial. Ignored while Require Staff Confirmation is on.

When enabled, Diski keeps a panel with a submit button pinned to the bottom of the suggestion channel, reposting it after new messages so members always have a one-click way to open the suggestion form.

The title shown at the top of the sticky submit panel embed. For example "Submit a Suggestion".

The body text of the sticky submit panel embed, shown beneath the title. Use it to tell members how or what to suggest.

The accent colour of the sticky submit panel embed, chosen as a hex value. Pick a colour that stands out in your suggestion channel.

The text shown on the sticky panel's submit button that members click to open the suggestion form. For example "New Suggestion".

An optional emoji displayed on the sticky panel's submit button, to the left of the label. Leave it blank for a text-only button.

The accent colour of each pending suggestion embed, chosen as a hex value. Approved suggestions turn green and denied suggestions turn red automatically.

The emoji shown on the upvote button of each suggestion. Members click it to add their upvote; clicking again removes it.

The emoji shown on the downvote button of each suggestion. Members click it to add their downvote; clicking again removes it.

When enabled, Diski opens a discussion thread on each new suggestion so members can talk about it without cluttering the channel.

When enabled, members can choose to submit a suggestion without their name being shown — the suggestion embed displays "Anonymous" instead of the author's tag.