> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/bot-commands/add.md). # /add ## Add Command ### Overview The `/add` command gives a user or a role access to the current ticket. Run it inside the ticket. ### Usage ``` /add [user:@user] [role:@role] ``` * **user** *(optional user mention)*: The user you want to add. * **role** *(optional role mention)*: The role you want to add. You can provide a user, a role, or both. You can only add a role on a text-channel ticket. You cannot add a role to a thread ticket. ### Description * **Grant access**: Adds the user or role to the ticket so they can view it and send messages. * **Pings**: The bot pings a user you add. The bot does not ping a role you add. ### When to Use It * When you need to bring another member or a staff role into the ticket. * When the ticket needs help from a different team. ### Permissions * You can use this command if you have Manage Channels or Manage Server, or you are the server owner, or you hold an authorized support role. Administrator also works because it includes those permissions. * The bot needs `Manage Channels` to update the channel. ### Examples ``` /add user:@JohnDoe ``` Lets John Doe view and send messages in the ticket. ``` /add role:@SeniorSupport ``` Gives the SeniorSupport role access to the ticket. This works on text-channel tickets only. --- # 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://ticketking.xyz/docs/bot-commands/add.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.