> 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/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).

# General tab

All items that utilise the Properties window to display/configure their attributes include a **General** tab, which is always the first tab in the name tabs area in the Properties window. The **General** tab displays by default when any Command Centre item is opened via the Properties option.

**Note:** The example screen shot below is for an HBUS Terminal, and while it will differ slightly for other items, the procedure is still the same.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c21fb3a8b29ac999e7143663fedce26b791ed15e%2Fhbusterminal_generaltab.png?alt=media)

1. Type in a **Name** (limited to 60 characters) for the Command Centre item and a logical **Description** (limited to 200 characters).

   **Note:** When an item is first created, the **Name** defaults to the item type name, plus a number on the end to ensure that there are no duplicate names, (e.g.HBUS Terminal 1). The number increments by one if an item of that type already exists with that number on the end.
2. Is there a **Short Name** field?

   <table><thead><tr><th width="78">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to Step 3.</td></tr><tr><td>yes</td><td><p>the <strong>Short Name</strong> is used by the Gallagher Mobile Connect App instead of the <strong>Name</strong>.<br><br><strong>Notes:</strong></p><ul><li>This field is limited to 16 characters. If you do not enter a short name, the system will automatically use the first 16 characters from the <strong>Name</strong> field when displayed on a mobile device.<br>In the case of Cardholder names displayed on a mobile device, the mobile device will use the first 16 characters from the <strong>Last Name</strong> field and then the <strong>First Name</strong> field, (e.g. If Cardholder Lillian Phillipson logs into the Gallagher Mobile Connect App her name will display as <strong>Phillipson, Lill</strong>).</li><li>The following characters should not be used in the <strong>Name</strong> or <strong>Short Name</strong> as they do not display correctly: <strong>\ ' | ~</strong></li></ul></td></tr></tbody></table>
3. Select the appropriate **Division** from the drop-down list.

   **Notes:**

   * When creating new items, the last division an operator used for creating or saving an item would normally populate the **Division** field. However, if the operator's last used division is not available, then by default the system will select the highest division that the operator has access to. If there is more than one division at the same level, then the system will select the division which was created first.
   * If you have not set up Divisions yet, you can add these to your item at a later stage.


---

# 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/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.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.
