> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/help-desk/settings.md). # Settings - [Ticket Category](https://docs.adminremix.com/help-desk/settings/ticket-category.md) - [Custom Ticket Builder](https://docs.adminremix.com/help-desk/settings/custom-ticket-builder.md): Build your own tickets or use our premade tickets. - [Types of Questions/Labels](https://docs.adminremix.com/help-desk/settings/custom-ticket-builder/types-of-questions-labels.md): We try to accommodate all our customers needs in our Custom Ticket Builder. Here is a list of all the types of questions and Labels and what they do/ look like to the end user. - [Ticket Rule](https://docs.adminremix.com/help-desk/settings/ticket-rule.md): Here is an explanation of the variation of rules that our system has and how to apply it to your team. These rules apply to users that are designated as Admin and have the Help Desk permissions. - [Options](https://docs.adminremix.com/help-desk/settings/options.md) - [Restricted Help Desk](https://docs.adminremix.com/help-desk/settings/restricted-help-desk.md): This is our view only for Help Desk. These are not allotted agents, but anyone you want to view open tickets. They do not have access to change the status, comment, create, update, or delete anything. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.adminremix.com/help-desk/settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.