> 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/viewer-configuration-overall-process.md).

# Viewer Configuration - Overall Process

### Introduction

This section describes the overall process for configuring Viewers in Command Centre. When necessary, this process refers to separate step-by-step procedures that are detailed elsewhere in this online help.

**Note:** Configuration of Site Plan Viewers differs from other viewers as their structure is different, (i.e. they do not have a Navigation Panel, nor do they use tiles). See [Configuring a Site Plan Viewer](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/viewer-configuration-overall-process/configuring-a-site-plan-viewer.md) for the procedure on configuring Site Plan Viewers.

### Operator Privileges

Operators with the "Configure Viewer" operator privilege can create, edit and delete Viewers in a particular division. They can also look at the Configuration of Viewers in that Division. Operators also require the "View Site" operator privilege to look at the Configuration of Viewers in that Division.

### Process

1. Select the **Viewers** tab on the Command Centre title bar.
2. Click the **Viewer Configuration** button on the toolbar.

   The Configuration Viewer displays with the Configuration Navigation Panel down the left hand side, and the Configuration Panel on the right.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-95fd0874454dcc064e88a46b1202be799f22f8e9%2Fnewviewerconfiguration.png?alt=media)

   The Configuration Panel is populated with the Viewer and Panel that the user was looking at in the application prior to clicking the **Viewer Configuration** button. The corresponding Viewer entry is highlighted in the Configuration Navigation Panel.

   The Configuration Viewer is divided into the following sections:

<details>

<summary>Configuration Navigation Panel</summary>

This displays all Viewers that the user has the privileges to either edit, or view the configuration for. By default, the list shows all Viewers grouped by Viewer Type, however the **Choose Filter By Division** button allows a site to display only those Viewers stored in a particular Division or any of it's sub-Divisions. The list can be expanded or collapsed using the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-747dfaebb372a6f9aea53cdd307a078be822e21d%2Fexpandcollapsebuttons.png?alt=media) buttons, and the items are listed in ascending alphabetical order at each level. A warning icon ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-0da768aab78fcb7f8cf7593c2d0bced3e40b63c0%2Fwarning.png?alt=media) will appear next to the name of any Viewer that has not been assigned to at least one Operator Group.

Although the Division in which a Viewer is stored has no significance in terms of who can see it in operational mode, a site may still choose to organise their Viewers divisionally based on the operators who will be using them.

It is possible to work on and/or view an unlimited number of Viewers without having to save changes in the interim. Viewers with unsaved changes should be easily identifiable in the list as they are in **bold** and have a **\*** at the end of their name. This includes new Viewers that have not been saved at all. The entry that corresponds to the Viewer displayed in the Configuration Panel will appear as selected.

**Note:** If you close the application with unsaved changes or if you reload viewers with unsaved changes, they will be lost.

</details>

<details>

<summary>Viewer Navigation Panel</summary>

The content of the Navigation Panel varies depending on the type of Viewer displayed, and its configuration, (e.g. for an **Alarm Viewer** the Navigation Panel will be a list of Alarms, whereas for a **Cardholder Viewer** the Navigation Panel will be a list of Cardholders).

</details>

<details>

<summary>Viewer Panel</summary>

The Viewer Panel shows the tiles locations.

</details>

<details>

<summary>Click here for a description of the buttons on this screen</summary>

<table><thead><tr><th width="184">Button</th><th>Description</th></tr></thead><tbody><tr><td>Choose Filter By Division</td><td>Although the Division in which a Viewer is stored has no significance in terms of who can see it in operational mode, a site may still choose to organise their Viewers divisionally based on the operators who will be using them. This button allows them to display only those Viewers stored in a particular Division or any of it's sub-Divisions.<br>Regardless of which option is selected, the items are listed in ascending alphabetical order at each level.</td></tr><tr><td>General Details</td><td>Clicking this button causes the <strong>General Details</strong> pop-up to display, and the rest of the screen is disabled.</td></tr><tr><td>Assign to Operators</td><td>Clicking this button causes the <strong>Viewer Assignments</strong> pop-up to display, and the rest of the screen is disabled. This allows you to assign the Viewer to one or more Operator Groups. The pop-up also shows a list of Operator Groups a Viewer is currently assigned to.<br>By default no Operator Groups are assigned to a Viewer, and a Viewer can be saved with no Groups assigned.<br>In a multi-server environment, only local Operator Groups appear in the browse tool.</td></tr><tr><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-1917d0a2636ac19bbf408180779ffc8b8ea0cc89%2Fquicktipsbutton.png?alt=media" alt=""></td><td>Clicking this button provides <a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/viewer-configuration-overall-process/quick-tips-for-configuration.md">quick tips for configuration</a>.</td></tr><tr><td>Rename...</td><td>Next to the <strong>Currently viewing panel</strong> drop-down, this button allows the currently selected Panel to be renamed. Clicking this button causes the <strong>Enter the new name for the panel</strong> pop-up to display, and the rest of the screen is disabled. The current Panel name can be over-typed, but not left blank, and the name must be unique for the Viewer. The new Panel name will be updated anywhere it is referenced in the Viewer.<br>The options available in the <strong>Currently viewing panel</strong> drop-down will depend on the type of viewer being configured.<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-d9769240b802b699ea8558c062c8495268965458%2Fcurrentlyviewingpanel.png?alt=media" alt=""><br>All viewers, with the exception of the Monitor Site Viewer, can have an Independent Panel that can be configured to display when there are either no items selected or no items to display, (e.g. no alarms in queue, no Cardholder search performed, etc.).<br>This allows for the "grey space" in the Viewer Panel to be configured to show <em>independent tiles\*</em>, (e.g. Cameras, Site Plans, etc.).</td></tr><tr><td>New Viewer</td><td>Clicking this button displays a list of the Viewer types that can be created. By selecting the type of Viewer to be created, the <strong>General Details</strong> pop-up displays, and the rest of the screen is disabled.<br><br><strong>Note:</strong> If the user has created a New Viewer previously, the type of Viewer last created will be set as the default.</td></tr><tr><td>Copy Viewer</td><td>This operates on the Viewer displayed in the Configuration Panel. Clicking this button causes the Viewer to be replaced in the Configuration Panel with a copy of itself. The Viewer name is set to <em>'Copy of &#x3C;name of Viewer being copied>'</em>, and a corresponding entry appears at the appropriate place in the Viewer list. Each Panel belonging to the original Viewer is copied, and the copy of the original Panel being viewed is displayed and shown as the 'Currently Viewing Panel'.</td></tr><tr><td>Delete Viewer</td><td>This operates on the Viewer displayed in the Configuration Panel. When this button is clicked, the confirmation message <em>"Are you sure you want to delete &#x3C;Viewer name>?"</em> displays. On confirmation, the Viewer and associated Panels are deleted from the database, and the corresponding entry removed from the Viewer list.<br><br><strong>Note:</strong> This button is only enabled if the Viewer has been saved to the database.</td></tr><tr><td>Revert to saved</td><td>This operates on the Viewer displayed in the Configuration Panel. Clicking this button causes all changes made to the Viewer (and associated Panels) to revert to the state they were in following the last save.<br><br><strong>Note:</strong> This button is only enabled when the Viewer (including its Panels) has unsaved changes.</td></tr><tr><td>Save</td><td>This operates on the Viewer displayed in the Configuration Panel. Clicking this button validates the Viewer (and associated Panels), before saving changes to the database.<br><br><strong>Note:</strong> This button is only enabled when the Viewer (including its Panels) has unsaved changes.</td></tr><tr><td>Work in full screen config view</td><td>Clicking this button causes the Viewer Configuration Preview to be displayed in full screen mode, in accordance with the screen resolution selected. The maximised version of the panel layout allows you to configure the layout of the Viewer Navigation Panel and Viewer Panel in the same way as if you were working in the minimised version.<br>From here you can save changes, and easily navigate back to the minimised version by clicking the <strong>Return to normal config view</strong> button.</td></tr></tbody></table>

{% hint style="info" %}
**\*Independent tiles**

Some of the tile types can operate independently from a Viewers Navigation Panel, and can therefore have static configuration (or allow Operator selected). These tiles can be placed on any viewer.
{% endhint %}

</details>

3. Create/edit a Viewer.

   Refer to [Creating a new Viewer](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/viewer-configuration-overall-process/creating-a-new-viewer.md) for the procedure.
4. Configure the content of the Viewer Navigation Panel, (e.g. add and remove columns).

   Refer to [Configuring the Viewer Navigation Panel](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/viewer-configuration-overall-process/configuring-the-viewer-navigation-panel.md) for the procedure.
5. Configure the Tiles for the Viewer.

   Refer to [Configuring Tiles](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/viewer-configuration-overall-process/configuring-tiles.md) for the procedure.
6. Click the **Save** button.

   **Note:** Although this saves a new Viewer or changes made to any existing Viewer, the changes do not appear immediately in operational mode. By right clicking on the **Viewer Configuration** button and selecting **Reload Viewers**, the changes appear without logging off and on again.


---

# 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/viewer-configuration-overall-process.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.
