From 1e810f24d2706166e5de06f3a1a79891da9afb3c Mon Sep 17 00:00:00 2001 From: biast12 <53872542+biast12@users.noreply.github.com> Date: Tue, 8 Sep 2026 23:34:40 +0200 Subject: [PATCH] Clarify server-wide vs panel ticket limits MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Updates dashboard and setup docs to explain that ticket limits are enforced in two independent places: a server-wide Simultaneous Ticket Limit and each panel’s Max Open Tickets Per User. Adds cross-links, a new explanation of how both limits combine, and removes outdated migration guidance that implied the per-user limit moved entirely to panel settings. --- docs/src/en/dashboard/settings/settings.md | 7 ++++++- docs/src/en/dashboard/ticket-panels.md | 8 +++++++- docs/src/en/setup/configuration.md | 2 +- 3 files changed, 14 insertions(+), 3 deletions(-) diff --git a/docs/src/en/dashboard/settings/settings.md b/docs/src/en/dashboard/settings/settings.md index d36b3df..96978bf 100644 --- a/docs/src/en/dashboard/settings/settings.md +++ b/docs/src/en/dashboard/settings/settings.md @@ -14,7 +14,6 @@ Several settings have moved to the per-panel editor. Each panel now controls its | Old Settings location | New location (panel editor section) | |---|---| -| Per User Simultaneous Ticket Limit | [Ticket Behaviour](/dashboard/ticket-panels#ticket-behaviour) (Max Open Tickets Per User) | | Allow Users to Close Tickets | [Closing and Claiming](/dashboard/ticket-panels#closing-and-claiming) | | Ticket Close Confirmation | [Closing and Claiming](/dashboard/ticket-panels#closing-and-claiming) | | Enable User Feedback | [Closing and Claiming](/dashboard/ticket-panels#closing-and-claiming) | @@ -55,6 +54,12 @@ Controls what happens when a ticket is switched to a different panel and the cur Click the info icon next to the label for a detailed explanation of each option. +### Simultaneous Ticket Limit + +The maximum number of tickets a single user can have open across the whole server at once (0-10, default 10). Set it to 0 for no server-wide limit. Staff members are exempt. + +It counts every open ticket, whichever panel it came from, and applies alongside each panel's own **Max Open Tickets Per User** rather than replacing it - see [how the two limits combine](/dashboard/ticket-panels#how-the-two-limits-combine). + ### Anonymise Dashboard Responses When enabled, all responses sent from the web dashboard appear as if they were sent by the bot rather than by the individual staff member. This hides the identity of the staff member responding. diff --git a/docs/src/en/dashboard/ticket-panels.md b/docs/src/en/dashboard/ticket-panels.md index 3b9cf8b..f242fca 100644 --- a/docs/src/en/dashboard/ticket-panels.md +++ b/docs/src/en/dashboard/ticket-panels.md @@ -260,7 +260,13 @@ A per-user cooldown preventing users from opening tickets on this panel in rapid ### Max Open Tickets Per User -The maximum number of tickets a single user can have open at the same time on this panel. Set to 0 for no limit (default). Maximum value: 10. Staff members are exempt from this limit. +The maximum number of tickets a single user can have open at the same time on this panel. Only tickets opened from this panel count towards it. Set to 0 (default) for no limit on this panel. Maximum value: 10. Staff members are exempt from this limit. + +#### How the two limits combine + +This limit and the server-wide [Simultaneous Ticket Limit](/dashboard/settings/settings#simultaneous-ticket-limit) are independent and both apply, so a user is blocked as soon as either is reached. A limit of 0 switches that check off; a user is only unlimited when both are 0. + +With a server-wide limit of 6 and this panel set to 1, a user can have at most 6 tickets open across the server, and at most 1 of those from this panel. ## Closing and Claiming diff --git a/docs/src/en/setup/configuration.md b/docs/src/en/setup/configuration.md index 751c762..e013024 100644 --- a/docs/src/en/setup/configuration.md +++ b/docs/src/en/setup/configuration.md @@ -17,7 +17,7 @@ There are two ways in which you can configure the bot: We recommend using the web dashboard to configure the bot, as it's easier and more settings are available - including ticket panels. ::: -`/setup` automatically creates the roles, channels, and category you need (excluding ticket panels) without any interaction required from you. This is fine as a starting point, but every other setting - ticket limits, transcripts, thread mode, welcome messages, and so on - is configured per panel on the web dashboard. +`/setup` automatically creates the roles, channels, and category you need (excluding ticket panels) without any interaction required from you. This is fine as a starting point, but every other setting - transcripts, thread mode, welcome messages, and so on - is configured per panel on the web dashboard. Ticket limits are set in two independent places that both apply: server-wide on the [Settings](/dashboard/settings/settings#simultaneous-ticket-limit) page, and per panel in the panel editor. We have guides on both of the available methods: