> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md).

# Deleting items

### Introduction

The procedure for deleting items in Command Centre Client is very similar for most items, as demonstrated by the following procedure.

**Note:** The system will only allow the deletion if the item is not used. If any site item is linked to the item you want to delete, (and hence is valid in the security operation of the site), you cannot delete it, (e.g. a Day Category used by a Schedule, a Schedule used to gain access to an Access Zone, etc.).

### Procedure

1. Click on the item you want to delete from the list in the Viewer Navigation Panel.
2. Click the **Delete \<item>** button.

   A confirmation message displays.
3. Click the **Yes** button to delete the item.

   The item disappears from the list in the Viewer Navigation Panel.

### Hint

{% hint style="info" %}
**Locating linked items**

If you attempt to delete an item that is linked to another item, a message will display, for example:

*"Changes have not been saved: This Schedule cannot be deleted as there is still a site item which depends on it for proper operation."*
{% endhint %}


---

# 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://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.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.
