> 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-a-low-credit-warning-signal.md).

# Configuring a low credit warning signal

After a prepay Cardholder is granted entry access to a Car Park that requires car parking credit, if the Cardholder's car parking credit is at or below the configured threshold, a warning event is generated.

This warning event can be used to activate a visual warning signal, (e.g. a red light located near the entry reader to the car park) to warn the Cardholder of their low credit status.

**Note:** The warning signal does not decrease the Cardholder's car parking credit.

### Using the Notifications feature of Command Centre

In addition to a warning signal, you can configure the Notifications feature of Command Centre to send a text message and / or email (when the warning event is generated) to the car park manager.

Refer to [Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notifications.md) for details about this feature.

To configure a warning signal, perform the following procedures in the Configuration Client:

<details>

<summary>Creating an Output</summary>

Create the Output (warning signal) that will activate after a prepay Cardholder is granted entry access to a Car Park that requires car parking credit, if the Cardholder's car parking credit is at or below the configured threshold.

You will need to ensure the Output is set to 'Pulse' when activated.

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

</details>

<details>

<summary>Creating a Macro</summary>

1. Create the Macro that will trigger the Output to activate.
2. Click the **Actions** tab.
3. Drag and drop the Output into the **Name** grid.
4. Select the Output in the **Name** grid and select Pulse from the **Override** drop-down list.

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

</details>

<details>

<summary>Creating an Action Plan</summary>

1. Create an Action Plan to trigger the Output.
2. Click the **Command Centre** tab.
3. Specify the priority of events or alarms generated, from the **Alarm Priority** drop-down list.

   When an event occurs the response will be of this priority.
4. Drag and drop the Macro to be triggered, into the **Macros** grid.

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

</details>

<details>

<summary>Assigning the Action Plan to a Door</summary>

Assign the Action Plan to the 'Soft Limit' Event Group on the entry Door to the Car Park.

When a 'Soft Limit' event occurs at the Door, the Output for this Door will be activated via the Action Plan and Marco.

**Note:** If required you can assign an Alarm Instruction to the 'Soft Limit' Event Group. *For example*, the Alarm Instruction may instruct the operator to warn the Cardholder of their low credit status.

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

</details>


---

# 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-a-low-credit-warning-signal.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.
