> 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/visitor-management/using-visitor-management/pre-registration-and-receptionist-functions/the-visit-screen/creating-a-visit/defining-access-for-a-visit.md).

# Defining access for a visit

Defining access for a visit

#### Introduction

The access defined for a visit controls what secure areas a visitor can access on-site, using the access card they have been assigned by the receptionist.

Access is defined in the visit but only granted once a visitor has been marked on-site. When a visitor is marked off-site or temporarily off-site, access is removed from the visitor.

**Notes:**

* When access is changed for a visit, access is changed for all visitors on the visit.
* If your site has designated exit readers for visitors to badge their cards at when leaving, they will need access to the exit zones, otherwise they will be denied access and will not be marked off-site.
* When defining access it may be important to have a generic access group selected that enables visitors to exit the site during an emergency.
* In the event some visitors require different access for the visit, these visitors should be assigned to a different visit.

#### Procedure

To define access for a visit, select one or more access groups by ticking the corresponding checkbox for each access group.

**Note:** This field is populated with a list of access groups valid for the selected visitor type.

#### Example

In the example below access has been defined for building 2.

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


---

# 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/visitor-management/using-visitor-management/pre-registration-and-receptionist-functions/the-visit-screen/creating-a-visit/defining-access-for-a-visit.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.
