> 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/custom-commands/editing-and-deleting.md).
# Editing and deleting commands
Editing, deleting, and turning commands on or off without deleting them.
:crown: **Premium feature.** The Custom Commands list page (sidebar, **Custom Commands**) shows every command you have created.
## Each command card
* **Edit** button, opens the editor with this command's settings loaded.
* **Delete** button, opens a confirmation step.
* **Enable/Disable** toggle, turns the command on or off without deleting it. The toast reads *"Command enabled successfully"* or *"Command disabled successfully."*.
* **Command name**, your reference name.
* **Command trigger**, the text users type.
* **Permissions pill**, a green *"All Staff"* pill or a blue *"N Role(s)"* pill.
* **Last edited or Created** date.
* A rendered preview of the response.
## Editing a command
Click **Edit**. The editor opens with this command's settings. Make your changes, then save. The audit log records that the command was updated.
## Turning a command off without deleting it
To stop a command from firing but keep its setup for later, use the **enable/disable toggle** on its card. A disabled command stays in the list, shown greyed out, and does not respond when the trigger is typed.
## Deleting a command
Click **Delete**. A confirmation appears:
> **Delete Command**
>
> Are you sure you want to delete the command ``? This action cannot be undone.
Confirm with **Delete**. While it deletes, the button reads *"Deleting..."*. The toast reads *"Command deleted successfully."*.
The command is removed from the list right away. The audit log records that the command was deleted.
## Search
The toolbar has a search box with the placeholder *"Search by command name or trigger..."*. It filters the list as you type.
## Empty state
When you have no commands yet:
> **No custom commands yet**
>
> Create custom commands that your staff can use to quickly respond to common questions.
>
> **Create First Command**
When a search matches nothing:
> **No matching commands found**
>
> Try a different search term or clear the search field.
## Permission to manage
To open this page and to create, edit, or delete commands, you need premium and the **Manage Commands** dashboard permission, or you must be the server owner or have Discord Administrator or Manage Server.
## Related
{% content-ref url="/pages/reYPizVLVHsc3ThwnHHX" %}
[Creating a custom command](/docs/custom-commands/creating-a-command.md)
{% endcontent-ref %}
{% content-ref url="/pages/ZrRf8S81rIkZBeccc3Wv" %}
[Limits](/docs/custom-commands/limits.md)
{% endcontent-ref %}
---
# 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/custom-commands/editing-and-deleting.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.
