> 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/icon-sets/understanding-icon-sets.md).

# Understanding Icon Sets

An Icon Set is a set of icons that is assigned to a particular object. The number of icons in a set can vary depending on the type of object. For example, an Input has three icons in its set to depict the various states, (i.e Open, Closed and Tampered).

There are default Icon Sets for all Command Centre items that can appear as an icon on a Site Plan. Operators with the "Edit Icon Sets" operator privilege can create new Icon Sets, as well as view, edit and delete existing Icon Sets. This gives operators more control over how icons are displayed on a Site Plan.

**Note:**

There are a number of Icon Editor software programs readily available online, via the Internet. To locate a suitable Icon Editor for editing and/or creating Icon Sets, go to Internet Explorer and search on "Icon Editors".


---

# 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/icon-sets/understanding-icon-sets.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.
