> 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/configuration-client/site-installation/universal-card-format/deleting-a-universal-card-format.md).

# Deleting a Universal Card Format

### Introduction

An operator wishing to delete a Universal Card Format must have the "Configure Site" privilege and be in the same Division (or a parent Division) as the Controller.

The Universal Card Format needs to be removed from any Controllers it is associated with prior to deleting it. The following procedure describes how to delete a Universal Card Format from Command Centre.

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Open the properties for the Controller that the Universal Card Format is associated with.
3. Click the **Card Formats** tab.
4. **Right click** on the Universal Card Format and select **Remove from List**.
5. Click **OK** to exit and save your changes.
6. Repeat Steps 2-5 for any other associated Controllers.
7. Click **Configure** from the menu bar, then **Universal Card Format**.

   The **Universal Card Format** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
8. Highlight the Universal Card Format you want to delete.
9. **Right click** and select **Delete**.

   A confirmation window displays.
10. Click **Yes** to delete the Universal Card Format.

### Result

The Universal Card Format disappears.

### Hint

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

If you attempt to delete a Universal Card Format that is linked to a Controller the following message will display:

"This Universal Card Format cannot be deleted, as it is assigned to a Controller."

The message however does not indicate which particular Controller(s) it is linked to, of which there could be many. Therefore a quick method of locating the Controller(s) is to use the [Find Tool](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#find-tool).

See [Example 2: Searching using Related To details](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/find-tool/examples/example-2-searching-using-related-to-details.md) for the procedure.
{% 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/configuration-client/site-installation/universal-card-format/deleting-a-universal-card-format.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.
