# Visitor Access

Visit access templates and visits work together to manage temporary access for visitors in Verkada Access Control. Templates define the rules and boundaries for visitor access, including schedules, doors, credentials, and duration limits. Visits are then created from these templates to grant individual visitors temporary access within those defined parameters.

{% hint style="danger" %}
You need **Access System Admin, Access Site Admin**, or **Access Site Manager** permissions to create and modify a visit access template.
{% endhint %}

***

## Visit Access Template

Visit access templates include the following settings:

* **Access Schedule**: Determines when visitor access is granted or denied.
* **Sites**: Specifies which sites the template applies to.
* **Doors**: Defines which doors visitors can access during their visit.
* **Max Duration**: Sets the maximum amount of time a visitor can access doors during a visit.
* **Credentials**: Defines which access methods visitors can use to unlock doors. Supported credential types include keycard, entry code, QR code, web unlock link, Face Unlock, and license plate.
* **Roll Call**: Includes visitors in all roll calls for the selected sites. Enabled by default.
* **Directory**: Defines which directories visitors created under the template are added to. Visitors are added to the Global Directory by default. Users with Directory Access, User Admin, or Manager permissions can select additional directories.

### Configuration

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

{% step %}
**In the left navigation, click Visitor Access > Access Templates.**
{% endstep %}

{% step %}
**In the top right, click Create template.**

1. Configure the options as needed.
2. Click **Save**.

{% hint style="danger" %}
Visitors will be unable to unlock doors if doors are added to a visit access template, but no credentials are enabled.
{% endhint %}
{% endstep %}
{% endstepper %}

{% hint style="info" %}
A visit access template can also be linked from a Verkada Guest Type. See [Door Access for Guests](/guest/configuration/door-access-for-guests.md) for more information.&#x20;
{% endhint %}

***

## Visits

Visits include the following information:

* **Visit Access Template**: The template on which the visit is based. This defines the configuration boundaries for the visit.
* **Start Time and End Time**: Defines how long the visitor has temporary access.
* **Credentials**: Specifies the access methods and credential numbers the visitor can use to unlock doors during the visit.
* **Doors**: Defines a subset of doors from the template that apply to the specific visit.
* **Visit Key Timeframe**: Determines whether credentials remain active for the full visit duration (multi-use) or expire shortly after first use (single-use). See Visit Key types below.

Once a visit access template is created for a site, designated staff can create individual visits from the template.

{% hint style="danger" %}

* You need **Org Admin**, **Access System Admin**, **Access Site Admin**, **Access Site Manager**, or **Access Site Visit Manager** permissions to create a visit.
* The **Access Site Visit Manager** role lets staff create, modify, and end visits across all templates at a site without granting broader Access Control admin permissions.&#x20;

See [Roles and Permissions for Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md#access-site-visit-manager) for more information.
{% endhint %}

### Configuration

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

{% step %}
**In the left navigation, click Visitor Access > Visits.**
{% endstep %}

{% step %}
**In the top right, click Create Visit.**
{% endstep %}

{% step %}
**Select a Visit Access Template.**

The template defines the doors, schedule, credential options, and maximum duration available for this visit.

{% hint style="info" %}

* **Org Admin**, **Access System Admin**, **Access Site Admin**, and **Access Site Managers** can create a Custom Visit independent of a Visit Access Template by selecting the Custom access template.
* Intercom receivers can create a Custom Visit limited to Intercom doors. See [Grant Temporary Access with Visit Keys](/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/visitor-access-visit-access-type.md) for more information.
  {% endhint %}
  {% endstep %}

{% step %}
**On Describe visit:**

{% hint style="warning" %}
This step is optional. If a visitor is not added to a visit, the Visit Key is still created, but must be manually shared with the visitor to grant temporary door access. Visitor movement in the building will not be accurately logged without their information present.
{% endhint %}

1. Search for or create a new visitor.&#x20;

{% hint style="warning" %}
You must enter a First Name and Email when creating a visitor.
{% endhint %}

2. Enter a unique visit name.
3. Click **Next.**

{% hint style="info" %}
A visitor can have only one active visit at a time. If the entered email or phone matches an existing active visit, you'll be prompted to either end the previous visit or cancel the new one.
{% endhint %}
{% endstep %}

{% step %}
**On Select doors:**

1. Select the doors to add to the visit.
2. Click **Next.**&#x20;
   {% endstep %}

{% step %}
**On Set timeframe:**

1. Choose **Multi-use Visit Key** or **Single-use Visit Key**.
2. Set the Start and End times.&#x20;

{% hint style="warning" %}
The visit must fall within the schedule and maximum duration defined by the template.
{% endhint %}

3. Click **Next.**&#x20;
   {% endstep %}

{% step %}
**On Select credentials:**

1. Manage the credentials that will be sent to the user.
2. Click **Next.**&#x20;

{% hint style="warning" %}
If the visitor's email or phone matches an existing permanent user, Verkada will not issue a new keycard, Face Unlock credential, or license plate for this visit. The permanent user must use their existing credentials. Entry codes, QR codes, and web unlock links are still issued and delivered to the user by email. See [Credential delivery](#credential-delivery) below for more information.
{% endhint %}
{% endstep %}

{% step %}
**On Prepare Visit Key:**

1. Confirm the visitor's contact information.
2. (Optional) Add a welcome message.
3. Click Send Visit Key.

{% hint style="success" %}
The visit is automatically started the first time any of their credentials is accepted at a door.
{% endhint %}
{% endstep %}
{% endstepper %}

***

## Manage Visit Keys

The visitor is sent an SMS, an email, or both, depending on the contact information provided. Both link to a hosted Visit Key webpage that shows:

* The organization, start time, and end time of the visit
* The doors that the visitor can access
* All credentials issued for the visit and how to use them

The visit is automatically started the first time any of their credentials is accepted at a door.

{% tabs %}
{% tab title="View visit details" %}

#### View visit details

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

{% step %}
**In the left navigation, select Visitor Access > Visits.**
{% endstep %}

{% step %}
**Each Visit Key appears as a row in a table. When you select a visit, you can view the following information:**

* **Details**
  * **Doors:** Displays the doors the visitor can access
  * **Timeframe:** Shows when the Visit Key is active
  * **About:** Shows when the Visit Key was created and who created or last modified it
* **Visit Key**
  * **Credentials:** Displays the credentials provisioned for the visitor
  * **Welcome Message:** Shows the configured welcome message for the visitor
  * **Preview Visit Key:** Provides a preview of the Visit Key
* **Events:**&#x20;
  * Access event history tied to the Visit Key
    {% endstep %}
    {% endstepper %}

{% hint style="warning" %}
&#x20;Visitors can appear in active roll call reports for the sites associated with their visit access template. They become valid for the roll call report upon first badge in and are removed when the visit ends. See [Roll Call Reports](/access-control/integrations-and-alerts/access-control-reports/roll-call-reports.md) for more information.
{% endhint %}
{% endtab %}

{% tab title="Duplicate a Visit Key" %}

#### Duplicate a Visit Key

{% hint style="danger" %}
You can only duplicate visits in the **Awaiting arrival** and **Edded** states.&#x20;
{% endhint %}

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

{% step %}
**In the left navigation, select Visitor Access > Visits.**
{% endstep %}

{% step %}
**Select a visit from the list.**

**Awaiting arrival:**

1. At the top right, click <i class="fa-ellipsis">:ellipsis:</i> > **Duplicate**.
2. Edit the [steps](#create-a-visit-key) as needed.
3. Click **Send visit key.**&#x20;

**Ended:**

1. At the top right, click <i class="fa-copy">:copy:</i>.
2. Edit the [steps](#create-a-visit-key) as needed.
3. Click **Send visit key.**&#x20;
   {% endstep %}
   {% endstepper %}
   {% endtab %}

{% tab title="Edit Visit Keys" %}

#### Edit Visit Keys

{% hint style="danger" %}
You can only edit visits in the **Awaiting arrival** state.&#x20;
{% endhint %}

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

{% step %}
**In the left navigation, select Visitor Access > Visits.**
{% endstep %}

{% step %}
**Select a visit from the list in the Awaiting arrival state.**
{% endstep %}

{% step %}
**Click Edit next to sections on the Details and Visit Keys tabs to manage the configuration.**
{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="End a visit" %}

### End a visit

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

{% step %}
**In the left navigation, click Visitor Access > Visits.**
{% endstep %}

{% step %}
**Select a visit from the list.**
{% endstep %}

{% step %}
**In the bottom right, click Delete > Delete Visit.**

All credentials issued for the visit immediately stop working, and the visitor is notified via email or SMS.
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

***

## Credential delivery

The visit access template controls which credential types can be issued. Verkada supports the following options:

| **Credential**    | **Delivery**                   | **Notes**                                          |
| ----------------- | ------------------------------ | -------------------------------------------------- |
| **Keycard**       | Picked up at the front desk    | Add manually or via the scan-to-add modal          |
| **Entry Code**    | Email and Visit Key webpage    | Numeric code entered on a keypad reader            |
| **QR Code**       | Email and Visit Key webpage    | Can be added to Apple Wallet or Google Wallet      |
| **Web Unlock**    | Email and Visit Key webpage    | Single-tap door unlock from the visitor's browser  |
| **Face Unlock**   | Email link for self-enrollment | Face credential is deleted at the end of the visit |
| **License Plate** | Manual entry in the visit form | Requires an LPR camera at the door                 |

***

## FAQ

<details>

<summary>Can permanent users be granted visits to sites they do not have permission to access?</summary>

Yes. Permanent users can be added to a visit and use their existing credentials to access doors permitted by the visit access template. A permanent user can also receive a new entry code (if they do not already have one), a QR code, or a web unlock link for the visit. However, they cannot be issued a new keycard, Face Unlock credential, or license plate. Any temporary credentials issued for the visit expire when the visit ends.

</details>

<details>

<summary>Can a visitor have multiple concurrent visits?</summary>

No. Only one active visit per visitor is allowed. If you attempt to create a visit for a visitor who already has an active visit, you will be prompted to either end the existing visit or cancel the new one.

</details>

<details>

<summary>Can previously used credentials be assigned to a new visitor?</summary>

Yes. If the previous visit has expired, keycards and license plates can be reassigned. Entry codes, QR codes, web unlock links, and Face Unlock credentials issued to non-permanent visitors are deleted when a visit ends and are not reusable.

</details>

<details>

<summary>If multiple roll call reports are associated with a single site, will visitors with the configured visit access template appear in all reports?</summary>

Yes. Visitors with and without door access will appear in all roll call reports for the site.

</details>

<details>

<summary>What happens to a visit access template if a visit created from it is currently active?</summary>

Visit access templates cannot be edited while a visit derived from them is active or scheduled. You must either end the active visit or wait for it to expire before modifying the template.

</details>

<details>

<summary>Can I convert a visitor to a permanent user?</summary>

Yes. Visitors can be converted to permanent users from their profile while preserving visit history. Only one of First Name, Last Name, or Email is required to complete the conversion; other fields are optional. This action requires the Access User Manager or Access User Admin role. The Access Site Visit Manager role cannot convert visitors to permanent users.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.verkada.com/access-control/access/visitor-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
