> 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/~/revisions/EoCxP3hpfoyJZDsFs6y8/configuration/door-access-for-guests/assigning-a-keycard-in-guest.md).

# Assigning a Keycard in 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.

***

## Assigning keycards to visitors in Guest

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="/files/J0om6GyZ0702yNHfeepE" alt="" data-size="line"> **Guest.**
{% endstep %}

{% step %}
**On Guest Home, next to a visitor log, click Assign Keycard.**

<figure><img src="/files/ObJ8scL3e2O6746LddKz" alt=""><figcaption></figcaption></figure>
{% 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.

<div align="left"><figure><img src="/files/CMyBznSZLPiFQZB7bdl8" alt="" width="188"><figcaption></figcaption></figure></div>

{% hint style="danger" %}

* You need both **Workplace Site Viewer** and **Access Control Site Viewer** roles to assign keycards by scanning a card with a reader.
* You need at least the **Workplace Site Viewer** role to assign keycards to guests by manually entering a card number.
  {% endhint %}
  {% endstep %}

{% step %}
**Click Close.**
{% endstep %}

{% step %}
**Provide the keycard to the visitor 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="/files/5YzPj2rDv3mBhX0KhmOa" alt="" data-size="original">
{% endhint %}

### Assign keycards to invited guests

Keycards may only be assigned to [invited visitors](/guest/~/revisions/EoCxP3hpfoyJZDsFs6y8/configuration/guest-events.md) after they are signed-in.

***

## FAQ

<details>

<summary>What permissions are required to use the <strong>Scan Card</strong> feature?</summary>

The Guest user must also have the **Access Control Site Viewer** role in order to activate a keycard by scanning it on a reader.

</details>

<details>

<summary>Which doors can a Guest user scan a keycard on?</summary>

Guest users can select any door in the site when scanning a keycard.

</details>

<details>

<summary>Can new keycards be assigned to visitors who match existing Access Control users? </summary>

No, Guest users will not be able to assign new keycards to visitors whose contact information matches an existing Access user. In this case, the visitor can simply use their existing keycard to temporarily access doors as part of their visit.

</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/~/revisions/EoCxP3hpfoyJZDsFs6y8/configuration/door-access-for-guests/assigning-a-keycard-in-guest.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.