> 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-cardholder-access.md).

# Configuring Cardholder Access

To configure Cardholder access for Prepay Car Parks, perform the following procedure in Gallagher Configuration Client:

1. From the Gallagher Configuration Client main window, click **Manage** > **Cardholders.**

   The Cardholder List Window displays.
2. Right-click on the required Cardholder and select **Properties.**
3. Click the **Competencies** tab.

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

   **Note:** In order to view the current credit for the Cardholder, ensure you select the 'Car Parking Credit' Competency
4. Assign the 'Car Parking Credit' Competency to the Cardholder. Ensure the Competency status is set to 'Active'.
5. To configure limited credit for this Competency, check the **Has limited credit** checkbox.
6. Enter the Cardholder's credit into the **Current credit** field.

   **Notes:**

   * Operator changes to a Cardholder's car parking credit is logged by Command Centre operator events. Thus a Cardholder's car parking credit change history can be retrieved from Command Centre when required.
   * The current credit may be a negative value, indicating the Cardholder is in debt.
7. 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-cardholder-access.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.
