> 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-management/access-groups/temporary-access/granting-temporary-access-by-access-group.md).

# Granting Temporary Access by Access Group

### Introduction

This procedure details how to grant temporary access to members of an Access Group.

***

### Configuration

To configure temporary access, perform the following procedures in Gallagher Configuration Client:

1. Click **Manage** from the menu bar, then **Access Groups**.

   The **Access Group** 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 Group you want to add temporary members to.
3. **Right click** and select **Properties**.
4. Click each tab in turn to configure temporary access:

<details>

<summary>Cardholder Membership tab</summary>

1. Click the **Cardholder Membership** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5f0c012f1951e5daaac4733b2d4997bb3429dda0%2Fag_choldmembership.png?alt=media)
2. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens.
3. Select the cardholder(s) that you want to add as temporary members to the Access Group.

   Drag and drop them into the **Cardholder Membership** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6ea21bd55b0fe613b4e50e3366a1683ae5b27bd7%2Ftempchintogroup.png?alt=media)
4. Close the **Cardholder** List Window.
5. Highlight the cardholder (on the **Cardholder Membership** tab) that requires temporary access.

   The 'From' and 'Until' Date fields become enabled.

   **Note:**

   The order of the columns can be repositioned if you want, (e.g. you may find having the Date columns first useful so you can sort by date and see which cardholders have the same temporary access periods). See [Repositioning Column Headers](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view/repositioning-the-column-headers.md) for the procedure.
6. Click the 'From' drop-down box and select the date the cardholder needs access from.

   The 'From' Time Box becomes enabled, and the 'From' date now displays in the main grid beside the cardholders name.
7. Alter the time in the 'From' Time Box ![AlmZGeneralTab](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e4538d2407843d64dc424ee5b56ef583f213b62e%2Fmacro_timebox.png?alt=media) to the time the cardholder needs access from on this date.
8. Repeat Steps 9 and 10 for the 'Until' fields, (i.e. the date and time of the last day the Cardholder needs access up to).

   The 'Until' date displays in the main grid beside the cardholders name.

</details>

<details>

<summary>Membership Defaults tab</summary>

1. Click the **Membership Defaults** tab.

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

   By default, the start and end dates are set to none, meaning that by default, membership is permanent.
2. Do you want temporary members to be removed from the **Cardholder Membership** tab when their temporary access period expires?

   <table><thead><tr><th width="73">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>leave the <strong>Automatically remove expired memberships</strong> checkbox ticked.<br><br><strong>Note:</strong> By leaving the checkbox ticked, all expired memberships shall be deleted automatically from the list on the <strong>Cardholder Membership</strong> tab when they expire.</td></tr><tr><td>no</td><td>uncheck the <strong>Automatically remove expired memberships</strong> checkbox.<br><br><strong>Note:</strong> By unchecking the checkbox, cardholders with temporary access will remain in the list on the <strong>Cardholder Membership</strong> tab once their access period expires.</td></tr></tbody></table>

   **Note:**

   Cardholders can only belong to 255 unique, and active or pending, Access Groups.

</details>

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

### Result

An Access Group now has temporary member(s).

**Notes:**

* The cardholder(s) you have granted temporary access to will now have this Access Group displayed in the **Access Groups** tab of their properties.
* If two operators concurrently add the same temporary membership, (i.e. one via the Access Group properties and the other via the Cardholder properties), **two** new memberships will appear in both the **Access Group** and **Cardholder** properties.

  Two events will also be generated, indicating that separate operators created the new memberships.


---

# 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-management/access-groups/temporary-access/granting-temporary-access-by-access-group.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.
