> 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/configuring-licensable-features/car-park-management-configuration/creating-a-car-park.md).

# Creating a Car Park

The maximum number of car park spaces per site is 2000, and these 2000 car park spaces can be assigned to a single controller.

### Pre-requisites

Before proceeding with this procedure, ensure the following items have been configured:

* Divisions
* Controller 6000s
* Alarm Zones
* Doors

### Procedure

To create a Car Park, perform the following procedure:

1. From the Command Centre main menu, Click **Administration** > **Car Parks**.
2. Click the **New Car Park** button.

   The Car Park Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-ae73738136da6e39ee0eb51ebac8c24e7cb41e25%2Fcarparkconfiguration.jpg?alt=media)
3. Type in the Name, Car Park Description and select the Division.
4. Click the **Controller** button, then select the appropriate Controller.

   **Note:** We recommend that you use a dedicated Controller 6000 to run a Car Park and the Car Park doors.
5. Click the **Alarm Zone** button, then select the appropriate Alarm Zone.

   **Over-allocation queue**

   The over-allocation option grants access to a Cardholder who has a reservation, but the allocated Space is occupied by another Cardholder. Also, an Operator can configure the Car Park to raise an alarm if the Cardholder is still in the over-allocation queue after a configured period of time.
6. Do you want to allow any Cardholders in the over-allocation queue?

   If **Yes**, go step 7.

   If **No**, go to step 10.
7. Using the Spin Box or manually, enter the number of Cardholders allowed in the over-allocation queue.

   The Alarm configuration displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-580f5eef3c012cd52044c2f80fe59bfe18d7fce8%2Fcarparkviewer.png?alt=media)
8. Do want to raise an Alarm if a Cardholder is still in the over-allocation queue once the configured time is over?

   if **Yes**, go to step 9.

   If **No**, go to step 10.
9. Select the **Raise Alarm** check box, then enter the number of minute(s) after which an alarm is raised if the Cardholder is still in the over-allocation queue.

   **Note:** If the Raise Alarm check box is selected and the minute(s) is set to '0', as soon as a Cardholder enters the Car Park (via over-allocation) the following alarm is raised: "Time limit exceeded for \<Cardholder last name>, \<Cardholder first name> staying in the over-allocation queue of \<Car Park name>".
10. Click **Close**, then Click **Save**.

    **Notes:**

    * If an Alarm Zone is not assigned to the Car Park, the following message is displayed: "A Car Park cannot be saved without being assigned an Alarm Zone." Assign an Alarm Zone and try again.
    * Once a Car Park is created, you need to configure it. See [Configuring a Car Park](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/car-park-management-configuration/configuring-a-car-park.md) section.


---

# 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/configuring-licensable-features/car-park-management-configuration/creating-a-car-park.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.
