> 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/accessnow-release-notes/2025/june/host-a-visitor-workflow.md).
# Host a Visitor Workflow
Version d9ee3f8
### Overview
Employees can host visitors online in AccessNow, which removes the need to contact reception and saves time.
The system logs visitor details directly in Gallagher Command Centre and displays them in the Gallagher Visitor Management Reception Client. This streamlines visitor management, improves record accuracy, and reduces manual work.
### Prerequisites
Gallagher Visitor Management
Workflow-specific [Command Centre privileges](/knowledge-hub/accessnow-user-guide/system-administration/command-centre-integration/command-centre-accessnow-operator.md)
### Workflow options or customisations to consider
* What information will Reception need to know about the Visit?
* What sort of identification is required?
* Is an escort required? Is this person the same as the host?
* Who is making the request?
* Who are the visitors?
* What email notification do you want to send, and to whom?
* Does the visit need approval before being created in Gallagher Visitor Management?
* Does the visitor need Access?
### Workflow Overview: Employee View
{% stepper %}
{% step %}
Start a new request. Click **Host a Visitor**.\
\ 
{% endstep %}
{% step %}
**Create a Visit**
Complete the fields for the visit.\
{% endstep %}
{% step %}
**Add the Visitors to the Visit**
a) Click **Add Visitor**.
b) Complete the visitor details, then click **Add Visitor**.
c) Either **Add more visitors** or click **Next**.\
\
{% endstep %}
{% step %}
### Confirm Visitor Details
a) Check the visit and visitor details.\
b) Click **Create Visit**.
The visit is added to Gallagher Visitor Management.
{% endstep %}
{% step %}
**Edit or Close a Visit**
The visit remains in the requester's task list and can be edited or closed from there.
{% endstep %}
{% step %}
### Open the visit from **Tasks**.
{% endstep %}
{% step %}
### Modify or Close the Visit
{% endstep %}
{% endstepper %}
\
\
---
# 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/accessnow-release-notes/2025/june/host-a-visitor-workflow.md?ask=&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.
