> 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/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-transformation-mapping/access-group-transformation.md).

# Adding an Access Group transformation

### Introduction

When a source value is transformed, it can be used to change a cardholder's Access Group membership, either permanently or temporarily.

The source value will specify which Access Groups to add cardholders to, or which Access Groups to remove cardholders from.

**Notes:**

* The Access Groups you can map to are limited to the Access Groups present in Gallagher Command Centre.
* If an Access Group has a Required Personal Data Field assigned and a value has not been entered for the Required Personal Data Field, the cardholder will not be added to the Access Group until a value is entered.
* If the "Run As Operator" does not have both the "Modify Access Control" and "Edit Cardholder" privileges assigned for the Division the cardholder's Access Groups are in, then the cardholder record will fail to be imported.
* If a cardholder is added temporarily to an Access Group and the Temporary Access Group value and mapping remains, then each time the cardholder is imported another Temporary Access instance will be added (to the Cardholder's Access Groups tab).
* If an Access Group has been configured with a default "From" or "Until" date, the cardholder will receive these dates when added to the Access Group, if no other dates have been specified by the cardholder.

### Procedure

1. Create a transformation mapping to the Gallagher Command Centre Access Group Memberships field.
2. To add cardholder memberships, select **Add** from the Access Group membership action drop down list.
3. To remove cardholder memberships, select **Remove** from the Access Group membership action drop down list.
4. Click the **Add** button to add a transformation. The Add Transformation window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-72b0c09b86d86532e3a3f6fda1980a633a5ee697%2Ftransformationaccessgroup.png?alt=media)
5. In the upper field, enter the source value you wish to transform.

   **Note:** This field accepts wildcard characters. Refer to [Wildcard characters](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/wildcard-characters.md).
6. Select the Access Group whose membership you want to change and click the **Add** button.
7. To add additional Access Groups, repeat the above step.

   Cardholders will either be added to the Access Groups listed in the grid, or removed from the Access Groups listed in the grid.
8. To remove an Access Group from the grid, select the appropriate Access Group in the grid and click the **Remove** button.
9. To set a From date and time and Until date and time for all Access Groups listed in the grid, click the From or Until date drop down arrow and select either:
   * **Not mapped**. When added, the date and time will be set to the default Access Group Membership date and time. If a date and time has already been set, this value will remain unchanged.
   * **Fixed date**. Enter a date and time. The Until date and time must be greater than or equal to the From date and time.
   * **Source data field**. Select a source field to retrieve the date and time from.

     If you wish to specify a fixed From time or fixed Until time, check the "Use a fixed time of" check-box and enter a time. This time will override the time specified by the source field.
   * If the source field contains a date but not a time and the "Use a fixed time of" check box is unchecked, the time will be set at 0:00 hours on the From date and 0:00 hours on the Until date.
   * If the source field contains a time but not a date, then today's date will be used.
   * If the source field contains a non date value, the cardholder record will fail to import.
   * If the Until date and time is less than the From date and time, the cardholder record will fail to import.
   * If the source field contains a blank value, the From or Until date and time will not be set.
10. Click the **OK** button. Your transformation is added to the Transformations grid.
11. Repeat as necessary, to add additional transformations.

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

    **Note:**

    * If the source value doesn't match a transformation, refer to [Mapping a value that doesn't match a transformation](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/mapping-a-value-that-doesnt-match-a-transformation.md).
    * When mapping from a database, if the source field is a related data field containing multiple values, then each value will be processed in turn.


---

# 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/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-transformation-mapping/access-group-transformation.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.
