> 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/door-access-for-guests/manage-visitor-access-control-privileges.md).

# Manage Visitor Door Access from Guest

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.

***

## How door access is issued to visitors

[Visit Access Types](https://help.verkada.com/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/visitor-access-visit-access-type) defines which doors a visitors can access and what credentials a visitor can use to unlock those doors. Verkada Guest supports issuing visitors the following credentials:

1. [Keycards](https://help.verkada.com/guest/~/revisions/EoCxP3hpfoyJZDsFs6y8/configuration/door-access-for-guests/assigning-a-keycard-in-guest)
2. Unlock Links
3. Entry code
4. QR code
5. Face Unlock\*

{% hint style="warning" %}
In Guest, visitors can only be issued Face Unlock credentials if they sign-in at a **kiosk**.
{% endhint %}

Keycards must be assigned to visitors each visit by a Workplace user. Learn more about [assigning keycards to visitors](https://help.verkada.com/guest/~/revisions/xrJT73IOTfAWzozwLpVL/configuration/door-access-for-guests/assigning-a-keycard-in-guest). After signing in, visitors will automatically be sent a URL where they can access Unlock Links, entry codes, and QR codes.

<div align="left" data-with-frame="true"><img src="/files/hoZrEEvcQatvcPj3ysiC" alt="" width="188"></div>

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

<img src="/files/5YzPj2rDv3mBhX0KhmOa" alt="" data-size="original">
{% endhint %}

***

## Review visitor access privileges

Guest users can review information about a visitor's door access privileges directly from Guest.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Workplace >** <img src="/files/J0om6GyZ0702yNHfeepE" alt="" data-size="line"> **Guest.**
{% endstep %}

{% step %}
**Select a visitor. In the details panel, you can review the following:**

* Which credentials have been issued to the visitor (ex: keycards, Face Unlock, entry code)
* which doors a visitor has access to
* how long a visitor has door access
* Whether a visitor will be included in roll call reports

  <div align="left" data-with-frame="true"><img src="/files/AWTsZo0pSJ0jxAxur4iR" alt="" width="188"></div>

{% endstep %}
{% endstepper %}

***

## Deactivate visitor door access

### Automatic controls for door access

A visitor will automatically lose access to doors:

1. When the door is outside its access controlled [door schedule](/access-control/access/door-schedules-and-exceptions.md).
2. When the visitor attempts to unlock doors outside the access schedule defined by their [visit access type](/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/visitor-access-visit-access-type.md).
3. When the visitor has been signed in longer than the maximum access duration defined by their visit access type.
4. When a Guest Event ends (applies to invited visitors only).
5. The visitor is signed-out at the Guest site's *auto sign-out* time.

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

1. If a visitor is signed out.
2. If a visitor’s access is revoked.
3. When the visitor has been signed in longer than the maximum access duration defined by their visit access type.
4. 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="/files/J0om6GyZ0702yNHfeepE" 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.**

<div align="left"><figure><img src="/files/1r6xjeqCmnDL934s8wt0" alt="" width="188"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

***

<details>

<summary>Will visitors lose door access automatically?</summary>

Yes, visitors can automatically lose door access [five ways](https://app.gitbook.com/o/bkNVNKmzsORLGDsma54Q/s/ZyuELZr7uIcXX3WnjX0N/~/edit/~/changes/69/configuration/door-access-for-guests/manage-visitor-access-control-privileges#automatic-controls-for-door-access).

</details>

<details>

<summary>Can I revoke a visitor's door access without signing them out? </summary>

Yes, Guest users can revoke a visitor's door access without signing them out from the visit details panel on the Guest Home page.

</details>

<details>

<summary>Can a visitor keycard be reassigned?</summary>

Yes. Once a visitor is signed out or their access is revoked, their keycard can be reassigned to another visitor. A keycard can only be active for one visitor at a time.

</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 dynamically by asking a question.

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

```
GET https://help.verkada.com/guest/configuration/door-access-for-guests/manage-visitor-access-control-privileges.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
