> 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/remove.md).

# /remove

## Remove Command

### Overview

The `/remove` command takes away a user or role's access to the current ticket. Run it inside the ticket.

### Usage

```
/remove [user:@user] [role:@role]
```

* **user** *(optional user mention)*: The user to remove.
* **role** *(optional role mention)*: The role to remove.

Like `/add`, you can provide a user, a role, or both. You cannot remove a role from a thread ticket.

### Description

* **Remove access**: Removes the user or role from the ticket so they can no longer view it or send messages.
* **Keep it private**: Use this to keep only the relevant members in the ticket.

### When to Use It

* When the ticket no longer needs input from a certain user or role.
* When you added someone by mistake.

### 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

```
/remove user:@JohnDoe
```

Removes John Doe's access to the ticket.

```
/remove role:@SeniorSupport
```

Removes the SeniorSupport role from the ticket. You cannot do this on a thread ticket.


---

# 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://ticketking.xyz/docs/bot-commands/remove.md?ask=<question>&goal=<user_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.
