# /add ## Add Command ### Overview The `/add` command grants a specified user or role access to the current ticket channel. ### Usage ``` /add [user:@user] [role:@role] ``` * **user** *(optional user mention)*: The specific user you want to add. * **role** *(optional role mention)*: The role you want to add. *(You must choose either a user or a role—Or you may also provide both at the same time)* ### Description * **Grant Access**: Dynamically adds new participants (users or roles) to a ticket conversation. * **Fine-Grained Control**: Ideal if you need an additional staff member or specialized role’s input on the ticket. * **Only Pings Users**: The bot will ping the user that has been added to the ticket. Roles added to the ticket **WILL NOT** be pinged. ### When to Use It * Whenever you need to bring an external user or specialized staff role into the conversation. * If the conversation requires escalation to a different department or team. ### Permissions * Usually staff or the original ticket creator can use it (depending on your server’s config). * Bot needs `Manage Channels` to adjust channel permissions. ### Examples ``` /add user @JohnDoe ``` Allows John Doe to view and participate in the ticket channel. ``` /add role @SeniorSupport ``` Grants the “SeniorSupport” role access to the ticket. --- # Agent Instructions: 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: ``` GET https://docs.ticketking.xyz/bot-commands/add.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.