> 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/lvlreq/level-requirements.md). # Level Requirements Level requirements locks a ticket panel behind a level, this is useful if you have priority support to users with high levels, or to make less troll tickets by making users need to be active, for obvious reason we dont recommend using this for report tickets ## How to use In /ticket-setup you'll see 2 options that are relevant to this article\ \ **Level Config:** This is the leveling service that we'll connect with to ensure a user has the level needed to open the ticket, we currently support [Kiai](/ticketsdocs/lvlreq/kiai.md)and [Amari](/ticketsdocs/lvlreq/amari.md) **Level Req:** This is the level a user to must have or exceed to use this ticket. After setting these we'll make sure to call the respective API whenever someone tries to open a Ticket, if they dont have level required Tickets will not allow them to create it ## How to setup leveling services Some bots may require authorization, you can check out each one in these respective articles **Kiai:** [Kiai](/ticketsdocs/lvlreq/kiai.md) **Amari:** [Amari](/ticketsdocs/lvlreq/amari.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/lvlreq/level-requirements.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.