> 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/using-command-centre/licensable-features/car-park-management.md).

# Car Park Management

The 'Car Park Management' feature allows Command Centre to manage Cardholders access to car parks. Using the Car Park Management feature, you can allocate Car Park Spaces to different groups of Cardholders. See the Car Park diagram.

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

This feature enables you to (in the Command Centre Client):

* create Car Parks, Spaces, and Sections
* allocate/remove Spaces to/from Cardholders and/or Access Groups
* deny access to the Car Park, if the allocated Space is already occupied by another Cardholder (i.e. shared Car Park Space) or grant access via an over-allocation queue
* grant access to certain Access Group(s) without reservation and,
* override Car Parks, Sections, and Spaces to empty.

**Note:** The Car Park Management feature offers different functionality from the Prepay Car Parking feature in the Configuration Client.

***

### Licensing

The 'Car Park Management' is a licensable feature, i.e. your license file must contain the following option:

`[Limits]`\
`Car Park Spaces=X` (Where `X` is the maximum number of Spaces that can be created)

***

### Operator Privileges

An Operator requires the appropriate Car Park privileges to perform Car Park tasks.The privileges only apply within the Divisions assigned to that Operator Group.

<table><thead><tr><th width="270">Operator Privilege</th><th>is required to...</th></tr></thead><tbody><tr><td>Edit Car Park Spaces and Assignments</td><td>create, edit and delete Car Park Spaces and assign cardholders to Spaces</td></tr><tr><td>Edit Car Parks and Sections</td><td>create, edit and delete Car Parks and Sections</td></tr><tr><td>Manage Car Park Assignments</td><td>create, edit and delete cardholder space assignments</td></tr><tr><td>Override - Empty Car Park Space</td><td>override Car Parks Spaces to empty</td></tr><tr><td>View Car Park Spaces and Assignments</td><td>view Car Park Spaces and cardholders space assignments</td></tr><tr><td>View Car Parks and Sections</td><td>view Car Park and Section details</td></tr></tbody></table>

***

### Multi- server

The following Command Centre multi-server functionalities can be achieved from a local server:

* view remote Car Parks, Sections, Spaces, total number of spaces, and allocation counts
* allocate/remove remote Spaces to/from Cardholders and/or Access Groups
* override remote Car Parks, Sections and Spaces to empty.

***

### Reports

Car Park Management has introduced the following columns which can be used within a Cardholder Report or an activity report:

* Car Park
* Car Park Section
* Car Park Space

***

### T20 Terminal Messages

When a Cardholder is granted or denied access to a Car Park, the T20 Terminal displays a pre-configured message. The messages cannot be customised.

[T20 Terminal messages](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/car-park-management-configuration/car-park-t20-terminal-messages.md)

***

### Using the Car Park Management

To use this feature, refer to the following topics:

[Car Park Viewer](https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/licensable-features/car-park-management/car-park-viewer.md)

[View Status and Overrides](https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/licensable-features/car-park-management/view-status-and-overrides.md)


---

# 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/using-command-centre/licensable-features/car-park-management.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.
