> 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/configuration-client/licensable-features/prepay-car-parking/configuring-the-prepay-car-parking-feature/configuring-a-prepay-car-park-group.md).

# Configuring a Prepay Car Park Group

To configure a Prepay Car Park Group, perform the following procedure in Gallagher Configuration Client:

1. From the Gallagher Configuration Client main window, click **Configure** > **Car Parks.**

   The Car Parks List Window displays.
2. Right-click and select **New\...Prepay Car Park Group.**

   The Prepay Car Park Group Properties window opens to the **General** tab by default.
3. Complete the fields as required. For further details see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-669ebdb963a6410b90b94a21bd2f0d79d316f236%2Fprepaycarparkgroup_setuptab.png?alt=media)
5. Select the 'Car Parking Credit' Competency, from the **Competency** drop-down list.

   If a Competency is not selected, then credit deduction does not apply to this group.
6. Enter the **Free parking duration**. (Default = 30 minutes. Maximum = 99 minutes)

   If the duration between the time a car enters a Car Park and the time the car exits the same Car Park is no longer than the free parking duration, the Cardholder is not charged.

   *For example*, if a Cardholder enters a Car Park but cannot find a car park slot, the Cardholder can exit the Car Park immediately without being charged.
7. Enter the **Charged parking duration**. (Default = 480 minutes \[8 hours]. Maximum = 9999 minutes)

   This is the period of time a Cardholder will be charged x credits.

   **Notes:**

   * A Cardholder may enter and exit the Car Parks belonging to the same group freely within this duration without being charged multiple times.
   * If a Cardholder exceeds the charged parking duration time, the Cardholder will be charged again.
8. Enter the **Credits to deduct**. (Default = 1 credit. Maximum = 9999 credits)

   This is the credit to deduct after the free parking duration time has passed since the car entered any of the Car Parks belonging to the group.

   **Note:** If the Command Centre Services are offline, Cardholders may not be immediately charged (credit deducted upon exit event) for car parking. The Cardholder will be charged when the services are restored.
9. Enter the **Credit warning threshold (soft limit)**. (Default = 3 credits. Maximum = 9999 credits)

   Each time a Cardholder is granted access to a Car Park, if the Cardholder's credit is at or below this threshold, a visual signal can be turned on to warn the Cardholder that their credit is low.
10. Select the action to take after a Cardholder runs out of credit, from the **When no credit remains** drop-down list. When a Cardholder's credit reaches zero the selected action occurs.

    Selectable actions are:

    * **No action**

      It is strongly recommended that you select this action if the 'Staff Car Park 1 Access Zone' enforces the 'Car Parking Credit' Competency. Otherwise, cars may queue behind a Cardholder who has been denied access.
    * **Expire competency**

      The Competency expiry date and time will be set to the date and time of when the Cardholder exits a Car Park Group, and credit was deducted, and the credit reaches zero.
    * **Disable competency**

      The Competency will be disabled. The expiry date and time for the Competency will remain, as previously configured. Hence if the Competency is re-enabled, the expiry date and time may still be valid.
11. Click **OK** to exit and save your changes.

    Click **Apply** to save your changes and stay in this window.

    Click **Cancel** to exit without saving your changes.


---

# 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/configuration-client/licensable-features/prepay-car-parking/configuring-the-prepay-car-parking-feature/configuring-a-prepay-car-park-group.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.
