> 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/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/visitor-access-visit-access-type.md).
# Visitor Access & Visit Access Type
Visit access types grant temporary access and credentials to guests managed by Verkada Guest.
{% hint style="danger" %}
You need [Access System Admin, Access Site Admin, or Access Site Manager permissions](/access-control/getting-started/roles-and-permissions-for-access-control.md) to create and modify a visit type.
{% endhint %}
***
### **Visit Access Type**
Visit access types contains the following information:
* **Access Schedule -** determines when access will be granted or denied for visitors.
* **Sites** - sites the visit access type applies to.
* **Doors** - set of doors visitors can access during their visit.
* **Max Duration -** maximum allocated time that a visitor can access the set of doors on a visit.
* **Credentials** - access methods that a visitor can use to unlock doors.
* **Roll Call** - visitors can be included in all roll calls for the selected sites.
### **Visit**
Visits contain the following information:
* **Visit Access Type** - The visit access type the visit will correspond to. This determines the configuration of temporary access.
* **Start Date and End Date -** the duration the visitor has temporary access.
* **Check In and Check Out Time -** the time a visitor is on site and can be included in roll call reports.
* **Credentials** - the access method and credential number visitors can use to unlock doors during their visit.
***
## Create a visit access type
{% hint style="danger" %}
You need to create your initial [visit access type](/guest/configuration/door-access-for-guests.md) in Guest before you can create one from the Access page.
{% endhint %}
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}
{% step %}
**In the left navigation, click Visitor Access.**
{% endstep %}
{% step %}
**In the top right, click Create.**
a. Configure the settings as needed.\
b. Click **Save.**
{% endstep %}
{% endstepper %}
{% hint style="danger" %}
Visitors will be unable to unlock the doors if doors are added to a visit access type but credentials (keycard or web unlock link) are not enabled.
{% endhint %}
***
## View visitor actions
Once guests are signed in and granted site access, their movements can be tracked on the door events page for the doors they are authorized to use.
Visitors can appear in an active roll call report for the sites associated with their visit access type. They become valid for the roll call report upon check-in and are removed from it upon check-out.
{% hint style="warning" %}
See [Roll Call Reports](/access-control/integrations-and-alerts/access-control-reports/roll-call-reports.md) for more information.
{% endhint %}
***
## FAQ
Can permanent users/employees be granted visits to sites they do not have permission to access?
Yes. Permanent users and employees granted visit access must use their existing credentials if their assigned visit access type permits door access.
Can a visitor have multiple concurrent visits?
No. Only one active visit per visitor is allowed.
Can I reuse credentials I have previously assigned to a visitor?
Yes. If the previous visit has expired, the credential can be reused.
What is the difference between a visit start/end date and check-in/out?
The start and end dates define the period during which the visitor had access to doors based on their visit access type. The check-in and check-out times indicate when the visitor was on-site and included in roll-call reports.
If multiple roll call reports are associated with a single site, will visitors with the configured visit access type appear in all reports?
Yes. Visitors with and without door access will appear in all roll call reports for the site.
---
# 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/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/visitor-access-visit-access-type.md?ask=&goal=
```
`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.