# Manage Visitor Access Control Privileges

The integration between Verkada Access Control and Guest enables organizations to grant limited door access to visitors. Organizations can issue access credentials to select visitors directly from Guest.

{% hint style="danger" %}
Keycards can only be applied to site-specific guest types.
{% endhint %}

***

## Assign door access to Visitors

Visitors can unlock doors using keycards or unlock links based on their visit access type settings.

### Keycards

{% hint style="danger" %}
You need at least Site Viewer permissions to assign keycards to guests.
{% endhint %}

When a visitor signs in with a Guest type with keycard access enabled, an option to assign a card appears in the visit log on the Guest Home page.

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products > Workplace >** <img src="https://1436127735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZyuELZr7uIcXX3WnjX0N%2Fuploads%2Fgit-blob-48822faa8f94922c3e3013291711e6f32a179087%2F8cf36b4c0ec5a908ea1110c7b552bf45536bc9f2.png?alt=media" alt="" data-size="line"> **Guest.**

{% endstep %}

{% step %}

#### On **Guest Home,** next to a visitor log, click **Assign Keycard.**

{% endstep %}

{% step %}

#### Assign access credentials:

a. On **Scan Card,** select a door in the site to scan the card on. Click to begin the scan. Scan the card at the selected door’s reader to register the card number in Command.\
b. On **Manual Entry,** ensure the card format is correct and enter the card number. Click to save.
{% endstep %}

{% step %}

#### Click **Close.**

{% endstep %}

{% step %}

#### Provide the keycard to the user to use during their visit.

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
A returning visitor can only be assigned new card credentials if they don’t have active door access from a previous visit. Guest will prompt staff to revoke access before a new card can be assigned.

<img src="https://1436127735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZyuELZr7uIcXX3WnjX0N%2Fuploads%2Fgit-blob-45673929bb4b80f6b457b4d2b2a96bdfc7b2b0ba%2Fb9db5502604661c56f7454086a6de84ba52ab760.png?alt=media" alt="" data-size="original">
{% endhint %}

#### Assign keycards to invited guests

Keycards may only be assigned to [invited visitors](https://help.verkada.com/guest/configuration-and-setup/guest-events/guest-events) when they are signed-in.

### Unlock links

{% stepper %}
{% step %}

#### Visitors will be sent a link to the visit portal via SMS or email once they sign in.

{% endstep %}

{% step %}

#### Select doors from the visit portal to remotely unlock them.

{% endstep %}
{% endstepper %}

![](https://1436127735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZyuELZr7uIcXX3WnjX0N%2Fuploads%2Fgit-blob-88efc8eb83d278a23f06ae11502b786f08d620de%2Fcc2fd34e9feeea5dccde13894a318ef8f740cf95.png?alt=media)

***

## Review visitor access privileges

Regular and invited visitors can access doors based on their Guest Type. Invited visitors can access doors 30 minutes before the event starts, with access revoked at the event’s end time.

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products > Workplace >** <img src="https://1436127735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZyuELZr7uIcXX3WnjX0N%2Fuploads%2Fgit-blob-48822faa8f94922c3e3013291711e6f32a179087%2F8cf36b4c0ec5a908ea1110c7b552bf45536bc9f2.png?alt=media" alt="" data-size="line"> **Guest.**

{% endstep %}

{% step %}

#### On **Guest Home,** you can review the following:

* how a visitor is allowed to open doors (physical credentials and/or unlock links)
* which doors a visitor has access to
* how long a visitor has door access for
* Whether a visitor will be included in roll call reports

  <div align="left" data-with-frame="true"><img src="https://1436127735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZyuELZr7uIcXX3WnjX0N%2Fuploads%2Fgit-blob-bd8edf64fff46fa8f9443b730872fa8e348c9f44%2F6ce3ad65d869ec363afa5cace1ca98d024d45245.png?alt=media" alt="" width="396"></div>

{% endstep %}
{% endstepper %}

***

## Deactivate visitor door access

### Automatic controls for door access

A visitor will automatically lose access to doors:

* When the door is outside its access controlled [door schedule](https://app.gitbook.com/s/aaHs5RfKqv9Z49mi02cC/configuration-and-setup/scheduling/door-schedules-and-exceptions).
* When the visitor attempts to unlock doors outside the access schedule defined by their [visit access type](https://app.gitbook.com/s/aaHs5RfKqv9Z49mi02cC/configuration-and-setup/visitor-access-visit-access-type).
* When the visitor has been signed in longer than the maximum access duration defined by their visit access type.
* When a Guest Event ends (applies to invited visitors only).
* If the visitor is signed out.

A keycard will be dissociated from a visitor and available to be re-assigned to other visitors:

* If a visitor is signed out.
* If a visitor’s access is revoked.
* When the visitor has been signed in longer than the maximum access duration defined by their visit access type.
* When a Guest Event ends (applies to invited visitors only).

### Explicitly revoke visitor door access

Guest users are able to revoke door access from a visitor directly from Guest.

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products > Workplace >** <img src="https://1436127735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZyuELZr7uIcXX3WnjX0N%2Fuploads%2Fgit-blob-48822faa8f94922c3e3013291711e6f32a179087%2F8cf36b4c0ec5a908ea1110c7b552bf45536bc9f2.png?alt=media" alt="" data-size="line"> **Guest.**

{% endstep %}

{% step %}

#### On **Guest Home**, Guest users have 2 options for revoking door access\*\*:\*\*

a. Select a signed-in user and click **Revoke Access**. When this option is selected, visitors will still be treated as signed in.\
b. Select a signed-in user and click **Sign out.**
{% endstep %}
{% endstepper %}

***

## Permission considerations

A Guest user’s ability to assign keycards, revoke access, and sign out visitors depends on visit access type. When a visit access type is configured with only doors from a single site:

{% hint style="warning" %}
You need at least Workplace Site Viewe**r** role for the site to manage visitor door access.
{% endhint %}

### Cross-site visit access types

Organizations may configure visit access types with doors from multiple sites so that visitors can use doors across sites. Two models are outlined below for permissioning Guest users so that they can perform actions that affect a visitor’s door access when the door access is defined by a cross-site Visit Access Type.

#### Visit Access Type spanning a parent site and one or multiple subsites

Organizations may dedicate a parent site for Guest and Access Control, but also use Access Control products in nested subsites. Organizations can design Visit Access Types to span both the parent site and subsites. In this case:

{% hint style="warning" %}
A Command user can perform actions that affect a visitor’s door access if they have at least the **Workplace Site Viewer** role for the parent site.
{% endhint %}

#### Visit Access Type spanning one or multiple independent sites

Organizations can configure a Visit Access Type to include doors from multiple parent sites.

{% hint style="warning" %}
A Command user can perform actions that affect a visitor’s door access if both of the conditions below are satisfied:

{% stepper %}
{% step %}

#### All sites with doors included in the Visit Access Type are also Guest sites.

{% endstep %}

{% step %}

#### The Command user has at least the **Workplace Site Viewer** role for all sites the Visit Access Type encompasses.

{% endstep %}
{% endstepper %}
{% endhint %}

***

**Need more help?** Contact [Verkada Support](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/need-help/contact-verkada-support).
