> 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/using-command-centre/working-with-viewers/tile-actions/cardholder-personalised-actions-tile-actions.md).

# Cardholder Personalised Actions Tile actions

The Cardholder Personalised Actions Tile displays personalised actions for each cardholder. It allows Access Zones and associated Outputs or Macros to be added, edited or removed for the cardholder.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-610b62185951a990a2aabeb23a0fb50f04812088%2Fcardholderpersonalisedactions_operational.png?alt=media)

The configuration for when the action is to be initiated, (i.e. on 'Access Granted' or on 'Access Taken'), can only be edited in the Configuration Client (on the **Personalised Actions** tab of the Access Zone properties).

### Operator Privileges

An operator requires the "Assign Personalised Actions" privilege in the division of the output or macro, to be able to assign that item to the Cardholder Personalised Actions tile.

**Note:** The operator requires "View Site" or "Edit Site" in the division of the Access Zone to assign it to the tile.

**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.

### Tile Actions

<details>

<summary>Adding Actions</summary>

Personalised Actions can be added as follows:

1. Click on the **Add Actions** button.

   The Add Access Zone / Output or Macro Pairs pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a5737d6a3dc4d3843c94fa712fc1a1ca5b8eb918%2Fpersonalisedacrtions_add_step1.png?alt=media)
2. If necessary, search for the Access Zone(s) you want by entering characters in the **Search** field and/or refining the search mode and filters.

   The grid becomes populated with Access Zones that match the search criteria.
3. Click the checkbox next to each Access Zone you want to include, or click the **Select All** button if you want to include all zones.
4. Click the **Add Selection** button.

   The Add Access Zone / Output or Macro Pairs pop-up changes to show a list of available Macros and Outputs to select from.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2568fb024552b1b7d3cea6234df961fd178d0185%2Fpersonalisedacrtions_add_step2.png?alt=media)
5. Click the radio button next to the Output or Macro you want to use for the Access Zones you have selected.
6. Click the **OK** button.

   The pop-up closes and the selected Access Zone(s) and Output or Macro populates the grid.
7. Click the **Save** button.

   The Personalised Action is saved.

   **Note:** To remove a Personalised Action, select (highlight) the row of the Action you want to remove and click the **Remove** button. Multiple actions can be selected for removal by holding down the < **Ctrl** > key while each action is clicked on, and then clicking the **Remove** button.

</details>

<details>

<summary>Changing Outputs/Macros</summary>

The Outputs/Macros selected for a Personalised Action can be changed as follows:

1. Click on the row of the Output/Macro you want to change.

   The Output/Macro changes to a button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-9454eaa36079cd370468d9d6ac7f73309d8970b6%2Fpersonalisedacrtions_change.png?alt=media)
2. Click the Output/Macro button.

   A browse tool displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f23c2f44faa5cd75ffb2f91859b0f4e240824282%2Fpersonalisedacrtions_selectoutputmacro.png?alt=media)
3. Click the radio button next to the Output or Macro you want to use.
4. Click the **OK** button.

   The pop-up closes and the name of the button changes to reflect the name of the Output or Macro selected.
5. Click the **Save** button.

   The row is no longer selected (highlighted), and the Output/Macro is no longer displayed as a button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-36459601f40943ce0784b2f33c9a3411356c4fed%2Fpersonalisedacrtions_changed.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/command-centre-client/using-command-centre/working-with-viewers/tile-actions/cardholder-personalised-actions-tile-actions.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.
