Add to Discord
Docs/Configuration/Settings explained

Configuration

Settings explained

Understand every configuration option available for Docket and how to set each one from Discord using slash commands.

DocketNøyra Docket team
6 min read
May 17, 2026

Ticket config

Guild-level settings managed with /ticket-config subcommands.

Default number format

The template used to generate ticket display IDs when a ticket type has no format of its own. Uses {number} as the placeholder for the auto-incrementing counter.

  • Set: /ticket-config set-format
  • View: /ticket-config view-format
Tip

If no format is set at guild or type level, Docket falls back to the global default {number}, producing IDs like 1, 2, 3. See Number formats for the full template syntax.

Notification channel

The channel where Docket posts a ping embed (including the staff role mention) whenever a new ticket is created. Choose a staff-only channel your team actively monitors.

  • Set: /ticket-config set-notification-channel
  • View: /ticket-config view-notification-channel
  • Disable: /ticket-config clear-notification-channel
Tip

Make sure Docket has Send Messages permission in the notification channel, otherwise the embed will fail to post silently.

Ticket type settings

Per-type settings configured when you run /ticket-type create. Each type stores the following fields:

Name

The display name shown to users in the ticket type select menu when they open a ticket. Examples: General Support, Bug Report, Billing.

Warning

Names must be unique within the server. Attempting to create a second type with the same name will fail.

Description

Optional text shown alongside the name in the select menu. Use this to tell users when to pick this type — e.g., "Use this for in-game bugs and technical issues."

Number format

The ticket ID template for this specific type. Overrides the guild default. Use {number} or {number:04d} (zero-padded) as the counter placeholder.

  • BUG-{number:04d} → BUG-0001, BUG-0002
  • SUP-{number} → SUP-1, SUP-2

Staff role

The Discord role whose members can manage tickets of this type (join, add/remove users, update status, close). This role is also mentioned in the notification channel embed when a ticket of this type is created.

Tip

Only members with this role or the Administrator permission can manage tickets of this type. If no role is set, only admins can manage them.

Channels

One or more Discord channels where the ticket panel button will be available for this type. A separate panel is posted to each selected channel during setup.

Feedback settings

The feedback system is configured through the Docket dashboard, not via slash commands. See the Feedback collection page for the full settings reference.

Best practices

Role assignment

  • Assign a dedicated staff role to each ticket type so the right team gets pinged — avoid using @everyone or overly broad roles
  • Create ticket-type-specific roles if different sub-teams handle different request categories

Number formats

  • Use a prefix that identifies the ticket type at a glance — e.g., BUG- vs SUP-
  • Zero-padding (e.g., {number:04d}) keeps IDs the same visual width in transcript lists
  • The ticket counter is global across all guilds sharing the database — gaps in numbering are normal and expected

Notification channel

  • Keep the notification channel staff-only so role pings don't disturb regular members
  • Consider a dedicated #ticket-notifications channel separate from the ticket threads themselves