> 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/automatic-employee-check-in.md).

# Automatic Employee Check-In

Log visiting employees effortlessly with Guest

With Access Control, Guest can log visiting employees without requiring them to stop at a kiosk. When a visiting employee opens a door, Guest creates a visit record automatically.

Admins use access groups to define which employees Guest logs at each building. For example:

* Exclude groups for the building’s full-time staff.
* Include groups for employees who visit the building from another location.

This configuration gives Guest an accurate record of non-permanent employees on site.

### Before You Begin

Automatic Employee Check-in requires [Access Groups](/access-control/users-and-credentials/add-and-modify-access-groups.md) and access-controlled doors already configured in Command.

***

## Create an Automatic Employee Guest Type

{% hint style="danger" %}
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 **Automatic Employee Sign-in**.
   {% endstep %}

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

{% hint style="danger" %}
You must have **Access User Manager** and **Access Site Viewer** permissions to configure the Employee Door step. 
{% endhint %}

<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%2Fqds3ZN0tJaljZH4IrB4C%2Fimage.png?alt=media&amp;token=e3d71b4a-5dd6-43a4-b376-952a5ea99380" alt="" width="563"><figcaption></figcaption></figure></div>

1. Select the door(s) where an access granted event should trigger an employee check-in.
2. Specify which [Access Group(s)](/access-control/users-and-credentials/add-and-modify-access-groups.md) should be included or excluded from triggering check-in.
   {% endstep %}
   {% endstepper %}

***

## Automatic employee sign-in process

When an [eligible access user](/guest/configuration/employee-check-in-with-guest/automatic-employee-check-in.md) unlocks an admin-defined door, a visit record is automatically created in Guest. The user receives a sign-in notification via email and text. The visit record names the door the employee entered through and includes footage from the camera paired to it.

***

## FAQ

<details>

<summary>What has to be true for Guest to create an employee visit record automatically?</summary>

Guest will only automatically create employee visit records if:

1. An Automatic Employee Guest Type is configured for the site.
2. The access user opens a door that is configured for the Automatic Employee Guest Type. They must open the door using:
   1. Keycard
   2. Entry code
   3. License plate
   4. Face Unlock
   5. NFC
   6. Bluetooth
3. The user is either a member of the *included* access group(s) or not a member of the *excluded* access group(s). See [step 5 of Create an Automatic Employee Guest Type](#create-an-automatic-employee-guest-type) for more details.

</details>

<details>

<summary>How does Guest handle visiting employees who interact with the same door multiple times during a visit?</summary>

Additional visit records will not be created if an employee opens a door assigned to an Automatic Employee Guest Type, as long as they are signed in.

</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/automatic-employee-check-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.