> 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/administration-workspaces.md).

# Administration Workspaces

### Introduction

Command Centre is moving to a workspace model, (i.e. focused working areas built around the work an operator is doing). The Administration Workspace is the first, covering the day-to-day people and access work that site administrators do. It is available from the **Workspaces** tab in the Command Centre Client and runs on your site's Command Centre server, so it does not need an internet connection, the Gallagher Cloud or the API Gateway.

It is separate from Command Centre Web in the Gallagher Cloud. The two run independently and using one does not affect the other.

It can be used to:

* Find cardholders and view their details
* View a cardholder's activity and history
* Manage cards and credentials (printing and encoding are not available)
* Manage cardholder access
* Manage cardholders competencies
* Edit cardholder details and Personal Data Fields (PDFs)

**Notes:**

* The workspace runs inside the Command Centre Client, so it closes with the Client.
* Cloud-dependent features of Command Centre Web, such as Mobile Connect two-factor sign-in, do not apply.

### Before you begin

Two things control what you see. The first decides whether you see the **Workspaces** tab at all. The second decides whether the **Administration Workspace** is available inside it.

**Seeing the Workspaces tab**

The **Workspaces** tab is shown only to operators with the "View Workspaces" privilege. If you cannot see the tab, ask your Command Centre administrator to add this privilege to one of your Operator Groups.

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

**Seeing the Administration Workspace**

Inside the **Workspaces** tab, the Administration Workspace is shown only when both of these are true:

* You have at least the View Cardholders privilege.
* The Administration module is installed on your site. It is installed by default from Command Centre v9.60.

Other privileges control what you can do once you are in. For example, the **Activity** tab requires the "View Events" privilege, and changing a cardholder's details requires the relevant edit privileges.

**If you cannot see it**

<table><thead><tr><th width="220">What you see</th><th>What to check</th></tr></thead><tbody><tr><td>No <strong>Workspaces</strong> tab</td><td>You need the View Workspaces privilege.</td></tr><tr><td><strong>Workspaces</strong> tab, but no Administration Workspace</td><td>You need at least the View Cardholders privilege, and the Administration module must be installed (default from v9.60). Sites upgrading from an earlier version should ask their administrator.</td></tr></tbody></table>

Select the item below that you require further detail on:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-folder-open">:folder-open:</i> Opening the Administration Workspace</td><td><a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration-workspaces/opening-the-administration-workspace.md">Opening the Administration Workspace</a></td></tr><tr><td><i class="fa-user">:user:</i> Working with a cardholder</td><td><a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration-workspaces/working-with-a-cardholder.md">Working with a cardholder</a></td></tr></tbody></table>


---

# 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/administration-workspaces.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.
