> 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/receptionist-functions/performing-visitor-actions/signing-in.md).

# Signing In

### Introduction

The **Sign In** button allows a visitors status to change to 'Signed In'. This status is used at the Visitor Management Kiosk. If a receptionist 'Signs In' a visitor the host can badge their card at a Kiosk reader and mark the visitor on-site.

### Procedure

1. Select a visitor record.

   **Note:** The visitor's status must be either 'Expected' or 'Expected Back'.
2. Click the **Sign In** action button.

   The visitor's status prior to signing them in determines the result, as follows:

   <table><thead><tr><th width="168">If a Visitor has an...</th><th>then...</th></tr></thead><tbody><tr><td>'Expected' status,</td><td>their visit status will remain as 'Visit Scheduled', and they will remain on the <strong>Expected</strong> tab.</td></tr><tr><td>'Expected Back' status,</td><td>their visit status will remain as 'Visit in Progress', and they will move from the <strong>On-Site</strong> tab to the <strong>Expected</strong> tab.</td></tr></tbody></table>

   **Note:** If configured in Command Centre, a notification will automatically be sent, (i.e. an e-mail and/or sms message) to the Host and the Escort, if there is one.


---

# 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/receptionist-functions/performing-visitor-actions/signing-in.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.
