> 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-kiosk/visitor-management-kiosk-screens/staff-rapid-entry.md).

# Staff (Rapid Entry)

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

Internal employees who are visiting a site can gain quick entry to the site by selecting the **Staff** button (or similar) on the 'Welcome screen', then badging their card.

**Notes:**

* While 'Staff' is the default name of this button, the text is configurable in Command Centre.
* If the card badge does not identify a visitor then the following message displays:

  *"Your access card is not recognised at this kiosk. Press Cancel to sign in manually."*

  This often happens if the cardholder's division is not included in the **Find Visitors in these Divisions** grid on the [Visit Configuration tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/command-centre-site-configuration/configuring-visitor-management-setup/visit-configuration-tab.md), or the logged in operator does not have privilege to view the cardholder of the badged card.
* If they change host and the site host is configured for Notifications, the host will be notified.
* If the card badge identifies the person but they are not a member of the Rapid Visitor Type and the Rapid Host Type, they will be automatically sent to the standard visitor sign-in process.

### Rapid Staff Entry - Update your visit details

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

When the card badge identifies a visitor who is allowed to fast track their entry, then a visit is automatically created, with the visitor hosting themselves. The departure time for the visit is displayed on screen and can be updated if necessary (defaults to today).

The visitor can also change their host from this screen, if they want to be hosted by someone else, by clicking the **Change Host** button which opens the 'Who are you meeting with screen'.

If configured, this screen will not display for self hosting visitors (only).

The 'Induction screen' displays (if configured), or is skipped if the visitor has already viewed this material within the configured time-frame. Likewise, the 'Conditions of Entry screen' displays if configured.

### Rapid Entry - For your information

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

The final screen for Rapid Staff Entry indicates that sign-in is complete. The following actions occur:

* The label is printed if label printing is configured for the kiosk,
* The visitor is automatically marked on site,
* Any Access Groups configured for this visitor type are assigned to the visitor,
* Host Notifications will occur if configured for the kiosk AND the visitor has chosen a host other than themselves,
* A message displays on screen to confirm actions taken, (e.g. *"Thank you, you have been marked onsite"*).

Selecting the **Touch here to finish** button returns the kiosk to the 'Welcome screen'.


---

# 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-kiosk/visitor-management-kiosk-screens/staff-rapid-entry.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.
