> 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.md).

# Temporary Access

### Understanding Temporary Access

A cardholder can be a temporary member of an Access Group, (i.e. they are only a member for a specified period between the start and end date and time of the temporary membership). During this time, a cardholder with temporary access has the same rights as any other member of that Access Group.

Temporary access can be configured by Access Group or by individual Cardholder.

### Personal Data Fields

Any Personal Data Fields (PDFs) that belong to a particular Access Group can be associated with the cardholder as soon as the temporary access information is entered (not necessarily active), until the temporary access record is deleted. Therefore, if the temporary access records are never deleted, the temporary member will retain that PDF. If however the temporary access records are deleted the PDF will also be deleted for the cardholder.

*For example:*

A student may be enrolled in a course that does not start until June and requires special access and a particular piece of information that will be entered into a PDF. At the beginning of the year, this student enrols in the course and temporary access is set up to start at the beginning of the June and end in November. The cardholder would have the PDF added to their cardholder information and the data required may be entered at the start of the year even though it will not be required until later.

If the system is set to delete all temporary access after it has expired, the PDF would disappear from the cardholders information at the end of November when the access expired. If the system is NOT set to delete temporary access records, the cardholder would retain the PDF, until the records were manually cleared.

### Multiple temporary memberships

A cardholder can have several temporary memberships to the same Access Group.

*For example:*

A University has two courses that share a resource.

Course 1 runs from 14/02 to 21/04.

Course 2 runs from 18/03 to 25/07.

Students in both courses require access to a computer lab, and there are several students taking both courses. These students therefore require access to the computer lab from 14/02 until 25/07.

### In This Section

* [Granting Temporary Access by Access Group](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 Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/temporary-access/granting-temporary-access-by-cardholder.md)
* [Deleting Temporary Memberships](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/temporary-access/deleting-temporary-memberships.md)


---

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