> 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/products/cc-software/operate/visitor-management-client/receptionist-functions/the-home-screen/action-buttons.md).

# Action buttons

### Description

The action buttons are located at the bottom of the Visit or Home screens. These buttons enable you to perform an action for the selected visitor.

**Notes:**

* The selected reception controls what actions are displayed. This means that if you manage more than one reception the actions available may vary.
* Sign In, Mark On-Site and Leave Site actions are compulsory, all other actions are configured in Command Centre by your Command Centre administrator. If configured, some actions may be required before a visitor can be marked on-site, (e.g. A badge may need to be printed before a visitor can be marked on-site).

### Actions

![](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3c9fae9a10d2bc94228d3cf46f4d9688296f8680%2Fvm_actionsbuttons.png?alt=media)

### Function

This table explains the function of each action.

<table><thead><tr><th width="144">Action</th><th>Function</th></tr></thead><tbody><tr><td>Invite</td><td>Click to email a QR Code barcode (in an attached <strong>.png</strong> file) to a visitor.</td></tr><tr><td>Sign In</td><td>Click to sign a visitor in.</td></tr><tr><td>Print Badge</td><td>Click to print a badge for a visitor.</td></tr><tr><td>Assign Credential</td><td>Click to assign an access credential to a visitor.</td></tr><tr><td>Assign Card</td><td>Click to assign an access card for a visitor.</td></tr><tr><td>Biometrics</td><td>Click to capture the biometrics, (i.e. fingerprints or finger veins) of a visitor on a visit.<br><br><strong>Note:</strong> If biometric functionality has not been set up and this button is clicked, an error will display and Visitor Management closes.</td></tr><tr><td>Assign Escort</td><td>Click to assign an escort for a visitor.</td></tr><tr><td>Mark On-Site</td><td>Click to mark a visitor on-site.</td></tr><tr><td>Temp Off-Site</td><td>Click to mark a visitor temporarily off-site.</td></tr><tr><td>Leave Site</td><td>Click to mark a visitor off-site.</td></tr></tbody></table>

**Note:** An additional **Send Message** button will be available in the Action buttons if the site is licensed for Notifications. This button allows a Receptionist to send a manual notification (via email and/or SMS message) to a Host and/or Escort for a visitor or Tour Group.


---

# 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/products/cc-software/operate/visitor-management-client/receptionist-functions/the-home-screen/action-buttons.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.