> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/guest/configuration/employee-check-in-with-guest/manual-employee-check-in-using-employee-id.md).

# Manual Employee Check-in Using Employee ID

Guest can sign in employees using dedicated Employee Guest Types. Employees who sign in through Guest, such as when visiting a non-primary location, can identify themselves by entering their Employee ID or scanning the barcode on their badge, which encodes their ID.

### Before you begin

Employees can sign in only if their Command user profile includes an Employee ID. You can add this field manually or sync it from an identity provider during [user provisioning](/command/security/identity-providers/user-provisioning-field-requirements-and-formatting-rules.md). 

***

## Create a manual employee Guest Type

{% hint style="danger" %}

* You must have **Org Admin** permissions to create Global Guest Types.
* You must have **Workplace Site Admin** permissions to create site-level Guest Types. 
  {% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Workplace > Guest.**
{% endstep %}

{% step %}
**On the left navigation, click Guest Settings.**
{% endstep %}

{% step %}
**Under Guest Types, click Manage Guest Types.**
{% endstep %}

{% step %}
**In the top right, click Add Guest Type.**

1. Name the Guest Type.
2. In the templates menu, select **Employee.** 
3. Choose either **Employee** or **Assisted Employee Sign-in**.
   {% endstep %}

{% step %}
**Configure the Employee step**.

{% hint style="danger" %}
You must have at least the **Command User Viewer** role to configure the Employee step. 
{% endhint %}

Choose which [Command Groups](/command/users-and-permissions/manage-users-in-your-organization/manage-command-groups.md) and [Access Groups](/access-control/users-and-credentials/add-and-modify-access-groups.md) whose members can sign in through this Guest Type. Only employees in the selected groups will be able to sign in through this Guest Type successfully.

<div align="left" data-with-frame="true"><figure><img src="https://1436127735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZyuELZr7uIcXX3WnjX0N%2Fuploads%2FIc0VT9uZesvcvPdm0n8L%2Fimage.png?alt=media&amp;token=e12c37b1-fc79-4fce-af10-c88d16a9b9bf" alt=""><figcaption></figcaption></figure></div>

Employee Sign-in Guest Types support scanning a barcode from an employee's PACS card that represents their Employee ID. Use the **Scan ID** toggle in the Employee step to control this feature. Supported barcode formats are listed [here](#which-barcode-formats-can-the-guest-app-read-an-employee-id-from).
{% endstep %}

{% step %}
**(Optional) Add or remove other sign-in steps to the Guest Type.**

Employee Sign-in Guest Types can feature the following steps:

1. Contact Info
2. Choose Host
3. Badge Photo
4. Open Response Question
5. Multiple Choice Question
6. Video
7. PDF
8. Document
   {% endstep %}
   {% endstepper %}

***

## Manual sign-in process for employees

When signing in through an Employee Guest Type, employees will complete the Employee step first. If an employee does not know their employee ID, they can select the **Enter Your Name** option.

***

## Resolve employee visit issues

#### Employee ID issues

If an employee skips the Employee ID step during sign-in, a Guest user must review the visit in Command.

<div align="left" data-with-frame="true"><figure><img src="https://1436127735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZyuELZr7uIcXX3WnjX0N%2Fuploads%2FRZ3BdxD9P825T1245DsF%2FScreenshot%202026-09-25%20at%2010.24.19%E2%80%AFAM.png?alt=media&amp;token=309b6e10-1ba0-4575-a570-2113fbbb1199" alt="" width="563"><figcaption></figcaption></figure></div>

### Sign-in conflicts

If an employee checks in while another visit for them remains active at a different Guest Site, a Guest user must review the visit.

When the Guest user marks the employee as signed in, Guest signs the employee out of their previous visits.

***

## FAQ

<details>

<summary>Can the Employee Guest Types be used for mobile sign-in and Guest Events?</summary>

Yes, Employee Sign-in Guest Types can be configured for mobile sign-in and Guest Events. Admins can choose where and how Guest Types are used with [Guest Type visibility controls](/guest/configuration/configure-guest-types/control-guest-type-visibility.md).&#x20;

Assisted Sign-in Employee Guest Types are only supported for [Concierge Sign-in](/guest/configuration/configure-guest-types/control-guest-type-visibility.md#configure-guest-type-visibility).

</details>

<details>

<summary>Which barcode formats can the Guest app read an Employee ID from?</summary>

The Guest app can recognize the following barcode formats for employee ID scanning:

* Code 39
* Code 93
* Code 93 Extended
* Code 128
* Interleaved 2 of 5
* QR
* Aztec
* Data Matrix
* MicroPDF417
* Micro QR
* PDF417

</details>

<details>

<summary>Can I give visiting employees temporary door access to a non-primary location?</summary>

Yes, employees can be provisioned with temporary door access when visiting. The Employee Guest Type must be configured with a [Visit Access Template](/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/visitor-access-visit-access-type.md) that has appropriate door access enabled. Employees will be able to use existing credentials (keycards, Face Unlock, etc.), as well as web unlock links and temporary entry codes, to open doors.

</details>

<details>

<summary>What employee information gets pulled into Guest after sign-in?</summary>

Guest will pull the following fields from a Command user profile:

* First Name
* Last Name
* User Photo
* Email
* Phone Number
* Employee Title
* Department
* Company Name

</details>

<details>

<summary>Can visiting employees be included in Incident Response?</summary>

Yes, visiting employees who are signed in at the Guest site when a Response is launched can be included as evacuees. The Response Template must be [configured to track Visitors (from Guest)](/incident-response/configuration/create-response-templates.md#people) as evacuees.&#x20;

</details>

<details>

<summary>Can visiting employees be included in Roll Call reports?</summary>

Yes, visiting employees can be included in Roll Call reports. The Employee Guest Type must be configured with a [Visit Access Template](/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/visitor-access-visit-access-type.md) that has Roll Call enabled.

</details>

<details>

<summary>Do Employee Guest Types support Security Screening?</summary>

No, Employee Guest Types do not support the Security Screening step. Verkada’s Guest Security Screening is a visitor management tool and is not a “consumer report” as defined by the Fair Credit Reporting Act (FCRA). Verkada is not a consumer reporting agency. This screening information must not be used, in whole or in part, to determine eligibility for employment, promotions, retention, housing, credit, insurance, or any other purpose regulated by the FCRA. Customers are responsible for ensuring their use of this feature complies with all applicable laws.

</details>


---

# 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.verkada.com/guest/configuration/employee-check-in-with-guest/manual-employee-check-in-using-employee-id.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.