> 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/intercom/configuration/grant-temporary-access-with-visit-keys.md).

# Grant Temporary Intercom Access with Visit Keys

You can grant temporary access to visitors using Visit Keys to allow secure, time-limited entry through intercom doors without requiring a call.

* **Visitors** are temporary access users that administrators can invite, provision with credentials, and automatically deprovision. They are commonly used for contractors, delivery drivers, vendors, interviewees, and other short-term guests. 
* **Visit Keys** are a form of visitor access used specifically for intercoms. Administrators can send them via email, text, or web link to provide one-time or recurring access for visitors.

{% hint style="success" %}
Visitors can access both intercom doors and standard access control doors. This article focuses only on intercom visitor access. See [Visitor Access](/access-control/access/visitor-access.md) for more information on access control.
{% endhint %}

***

## Prerequisites

### Permissions

* You need **Org Admin** or **Site Admin** permissions to enable Visit Keys on an intercom.
* You need **Site Admin** or **Receiver** permissions for a site with Visit Key-enabled intercoms to create and view intercom Visit Keys. 

{% hint style="warning" %}
See [Roles and Permissions for Command](/command/users-and-permissions/roles-and-permissions-for-command.md) for more information.
{% endhint %}

### Device compatibility

Visit Keys are supported on:

* Intercoms configured as standalone single-door access controllers
* Intercoms paired with an access controller

They are **not supported** on:

* Intercoms configured in **Third-Party Door Mode**

### Credential types

A Visit Key can include one or more of the following credentials:

* **QR code** – Scan on intercom cameras
* **PIN code** – Use on TD63 PIN pads
* **Web unlock** – Unlock doors directly from a mobile phone
* **License plate** – Use LPR cameras tied to the intercom for automated unlocks
* **Keycard** –  Use keycards on access/intercom readers

***

## Create a Visit Key

### Enable Visit Keys

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

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

{% step %}
**At the top, click Intercoms > Add Intercoms.**

1. Select the intercoms you want to enable for Visit Key access.
2. Click **Apply.**
   {% endstep %}
   {% endstepper %}

### Create a Visit Key

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

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

{% step %}
**In the top right, click Create Visit > Intercom door access.**
{% 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. 

{% 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 Intercoms:**

1. Select the intercoms to add to the visit.
2. Click **Next.** 
   {% endstep %}

{% step %}
**On Timeframe:**

1. Choose **Multi-use Visit Key** or **Single-use Visit Key**.
2. Set the **Start** and **End** times. 
3. (Optional) If the start and end times span different calendar days, the **Restrictions** option appears. In the **Restrictions** menu, select the days of the week and set the daily active time range for the key.
4. Click **Next.** 
   {% endstep %}

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

1. Manage the credentials that will be sent to the user.
2. Click **Next.** 

{% 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) 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 **Create Visit.**

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

{% hint style="warning" %}
Review the [FAQ](#h_4bae6f8cb2) for common questions about adding a Visit Key contact.
{% endhint %}

***

## Manage Visit Keys

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

#### View visit details

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% 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:** 
  * Access event history tied to the Visit Key
    {% endstep %}
    {% endstepper %}

{% hint style="warning" %}
 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](broken://pages/79wglkDtSiYR7VrLoiqD) 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. 
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% 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 > Intercom.**
{% 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 > Intercom.**
{% 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>Are Visitors a type of access user?</summary>

Yes, a Visitor is a type of access user. When you create a new visitor during Visit Key setup, the system automatically generates a corresponding access user tagged as a Visitor. These records persist, allowing you to issue future Visit Keys to the same person without re-entering their information. Because each visitor functions as an access user, all access events tied to their Visit Keys can be audited and traced back to that individual.

**View Visitors**

In Verkada Command, go to All Products > Access. In the left navigation, click Access Users and Groups. In the search bar, filter for Visitors.

</details>

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://youtu.be/8OAfVwV6Nq4).
{% endhint %}


---

# 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 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/intercom/configuration/grant-temporary-access-with-visit-keys.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.