> 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/site-installation/access-zones/configuring-personalised-actions-for-access-zones.md).

# Configuring Personalised Actions for Access Zones

### Introduction

The Personalised Actions feature allows specific actions to be triggered for specific cardholders, upon being granted access to an Access Zone.

This procedure allows operators with "Edit Site" operator privileges to configure Personalised Actions. The available actions are running a Macro or Output status change. These actions can be assigned directly to a Cardholder or to an Access Group.

**Note:** The Personalised Actions feature does not support Lift Cars.

**IMPORTANT:**

* For personalised action macros to run successfully, the Controllers must be online with the CCFT server. If the CCFT server is shutdown or otherwise offline at the time of an access then any configured macro actions will not be run.
* For personalised action outputs to be switched successfully, the Controller hosting the output must be contacted by the Controller hosting the door. This means that if there is a network outage at the time of the access then any configured output actions will not be run if the outputs are on a remote Controller. Ideally, personalised action outputs should be located on the same Controller that is hosting the door hardware that provides the access.

### Procedure

1. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Highlight the Access Zone you want to configure Personalised Actions for.
3. **Right click** and select **Properties**.
4. Click the **Personalised Actions** tab.

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

   The grid on this screen allows you to create a list of Personalised Actions for this Access Zone.
5. Drag and drop either individual Cardholders or Access Groups, as required, from the appropriate List Window into the grid.
6. Highlight the Cardholder or Access Group you wish to assign an action to.

   The **Output or Macro** drop-down list becomes enabled.
7. Select the required **Output or Macro** from the drop-down list.

   Alternatively, drag and drop an output or macro from the appropriate List Window.

   **Note:** The following table provides a list of the types of pre-configured actions that can be assigned to Cardholders and/or Access Groups:

   <table><thead><tr><th width="222">Pre-configured action</th><th>can be achieved by...</th></tr></thead><tbody><tr><td>Trigger one or more outputs</td><td>assigning the output(s) directly to a Cardholder or Access Group on this tab.</td></tr><tr><td>Trigger a macro (to print a report, run a command or trigger further outputs</td><td><ul><li>assigning the macro directly to a Cardholder or Access Group on this tab, or alternatively</li><li>a macro can be triggered via an Action Plan associated with an output.</li></ul></td></tr><tr><td>Trigger an override of any sort, (e.g. Access Zone, Alarm Zone, output)</td><td><ul><li>assigning an output with an associated Action Plan that triggers a macro override, or</li><li>assigning the macro override directly to a Cardholder or Access Group on this tab.</li></ul></td></tr><tr><td>Raise an alarm from an output</td><td>assigning an output to a Cardholder or Access Group on this tab.</td></tr></tbody></table>
8. Repeat Steps 5 - 7 for other Personalised Actions as required.

   **Notes:**

   * For individual Cardholders, the action will only happen when that Cardholder accesses the zone. However, for Access Groups the action will happen when any member of that group accesses the zone.
   * Multiple actions can be configured for a single Cardholder or Access Group by creating additional list entries.
   * There is a limit of 250 unique Cardholders and Access Groups in the list of personalised actions. Each Cardholder or Access Group is counted only once, even if they appear multiple times, (e.g. an Access Group has eight actions against it but is only counted once).
9. Click the appropriate "Actions are triggered on" radio button to define what will trigger the personalised actions, as follows:

   * **Access granted** = Actioned on access granted to the zone.
   * **Access taken** = Actioned on access granted and taken to the zone.

   **Note:** This setting will apply to **all** the personalised actions for this Access Zone.
10. Click **OK** to exit and save your changes.

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

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


---

# 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/site-installation/access-zones/configuring-personalised-actions-for-access-zones.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.
