> 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/getting-started/restricting-system-view.md).

# Restricting System View

### Introduction

When an operator with the "Select System View" or "Advanced User" operator privilege logs on to Command Centre, their system view selection is retained from their last log off. Clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-21696e72ec0a06324b205d044b43d8eb573a6bd7%2Fsystemoperatorbutton.png?alt=media) button on the Command Centre toolbar and selecting **System View** allows an operator to change their view of the system, (i.e. change the Operator Groups that are in effect). Their system view is limited to the site items, cardholders, Personal Data Fields (PDFs) and operator privileges assigned to them from the selected Operator Groups.

What displays on the System view button is determined as follows:

<table><thead><tr><th width="178.11114501953125">The button will show...</th><th>if...</th></tr></thead><tbody><tr><td>All Groups</td><td>the operator’s current system view includes all Operator Groups available to the operator at this workstation (and there is more than one).</td></tr><tr><td>Restricted View</td><td>the current system view includes only some of the operator's Operator Groups that are available at this workstation.</td></tr><tr><td>[Operator Group Name]</td><td>the current system view includes only one Operator Group.</td></tr></tbody></table>

Note: If an operator's system view was restricted, (i.e. did not include **all** Operator Groups) when they last logged off, the next time they log on the **Select System View** pop-up will display automatically. This allows an operator to confirm their system view, by either retaining the existing view or altering it.

### Procedure

This procedure describes how an operator can restrict (change) their system view. For operators to be able to perform this procedure they require the "Select System View" operator privilege.

1. Click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-21696e72ec0a06324b205d044b43d8eb573a6bd7%2Fsystemoperatorbutton.png?alt=media) button on the Command Centre toolbar, and select **System View**.

   The Select System View pop-up displays.

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

   The selections already made on this screen reflect your current system view, and the list of Operator Groups at the top includes **all** Operator Groups that you belong to.

   Any Groups you are a member of that are subject to restriction will appear in the bottom list. Restrictions apply to:

   * any Operator Group you are a member of that is restricted to one or more Workstations (the Operator Group has been configured with Restrictions), where the workstation you are accessing System View from is not in that list.
   * any Operator Group that is configured for a Workstation Routing item that is currently routed to or away from the Workstation from which the user is accessing System View.
2. Select the Operator Groups that you want to include in your current system view. You can either check or uncheck individual Operator Group checkboxes, or use the buttons available.

   <table><thead><tr><th width="156">Button</th><th>Description</th></tr></thead><tbody><tr><td>Select All</td><td>Checks <strong>all</strong> the Operator Group checkboxes.</td></tr><tr><td>Deselect All</td><td>Unchecks <strong>all</strong> the Operator Group checkboxes.<br>If you belong to many Operator Groups, and you want to restrict your system view to only a few of them, this is a quick method of achieving that rather than unchecking all the groups you do not want to include in your view. Click the <strong>Deselect All</strong> button and then re-check the groups you want.<br><br><strong>Note:</strong> If you leave all Operator Groups unselected the <strong>OK</strong> button becomes disabled, forcing you to select at least one group.</td></tr><tr><td>OK</td><td>Saves the settings you have chosen, and closes the <strong>Select System View</strong> screen.</td></tr><tr><td>Cancel</td><td>Cancels the changes you made and closes the <strong>Select System View</strong> screen.</td></tr></tbody></table>

### Result

Your system view has been restricted.

**Note:** Changing System View in Command Centre Client does not affect what an Operator can see and do in Configuration Client, and vice versa.


---

# 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/getting-started/restricting-system-view.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.
