> For the complete documentation index, see [llms.txt](https://invomagic.gitbook.io/ticketsdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://invomagic.gitbook.io/ticketsdocs/tickets/ticketing-settings.md). # Ticketing Settings Tickets has settings you can change for all panels, these are known as Ticketing Settings and can be edited by running the `/ticketing settings` command, lets go over them ## Ticketing Settings ### User Ticket Limit Users have a maximum amount of tickets they may have open at any one time, by default this is set to 3 meaning that if a user has 3 tickets open they wont be able to open another one, you may change this setting at anytime ### Reset User Ticket Count For a number of reasons a user might not be able to open a ticket even though they have none 'open' this is most frequently because you or your staff have deleted a ticket channel (when you should have closed it) but it could also be because of a bug (although unlikely) if this is the case you can select this option to reset a selected users internal ticket count back to 0. ### Ticket Ratings Whether or not to enable Ticket Ratings, more information on that [here](/ticketsdocs/tickets/ratings.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://invomagic.gitbook.io/ticketsdocs/tickets/ticketing-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.