> 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/command-centre-site-configuration/configuring-visitor-management-setup/reception-actions-tab.md).

# Reception Actions tab

This tab allows you to configure the actions that will be available to Receptionists.

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

Configure as appropriate:

<table><thead><tr><th width="228">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Action</td><td><p>By default the following actions are not available to receptionists:</p><ul><li>Send Invitation</li><li>Print Badge</li><li>Assign Card</li><li>Capture Fingerprints</li><li>Assign Escort</li><li>Temp Off-Site</li></ul><p>If you require any of them to be available to receptionists, check the checkbox to the <strong>left</strong> of the required action(s).</p><p><strong>Notes:</strong></p><ul><li>The "Sign In", "On-Site" and "Leave Site" actions are permanently checked and disabled so they cannot be unchecked.</li><li>Enabling the "Capture Fingerprints" option results in a <strong>Biometrics</strong> action button appearing on the Visitor Management Visit or Home screens. If this button is clicked when biometric functionality has not been set up an error displays and Visitor Management closes. For further detail on configuring biometrics, see <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration.md">Morpho Biometric Integration</a>.</li></ul></td></tr><tr><td>Required when marking On-Site</td><td><p>The "Print Badge", "Assign Card", "Capture Fingerprints" and "Assign Escort" actions can be set as mandatory prior to a visitor being recorded on-site. To do this, check the <strong>Required when marking On-Site</strong> checkbox directly below the required action(s).</p><p><strong>Note:</strong> The <strong>Required when marking On-Site</strong> option cannot be selected for "Assign Card", "Capture Fingerprints" or "Assign Escort" if the visitor has been configured to be marked automatically onsite.</p></td></tr><tr><td>Visitor Card Type<br>Credential Type</td><td><p>These drop-down lists are only enabled when the “Assign Card” action has been checked. If enabled, a Card Type and/or Credential Type must be selected, (e.g. a card type for recyclable visitor cards).</p><p><strong>Note:</strong> Only one Card Type and Credential Type per Division can be selected.</p></td></tr><tr><td>Send SMS Verification Code</td><td><p>Checking this option allows the Registration Server to authorise cardholders’ mobile phones.</p><p><strong>Note:</strong> This makes a <strong>Mobile</strong> field appear on the Assign Credential pop-up in the Command Centre Client when registering mobile credentials for cardholders.</p></td></tr></tbody></table>


---

# 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/command-centre-site-configuration/configuring-visitor-management-setup/reception-actions-tab.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.
