# Import and Export Credentials with CSV
Users and their corresponding access credentials live in [Verkada Command](/command/getting-started/get-started-with-verkada-command.md). [Access Control Managers](/access-control/getting-started/roles-and-permissions-for-access-control.md) and Admins can import credentials into Command in bulk with an uploaded .csv \[or comma-separated value (CSV)] file, or export credentials from Command to a downloaded .csv file. Learn more about [Roles and Permissions for Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md).
{% hint style="warning" %}
Through the [User Import flow](/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/import-access-control-users-csv.md), you can still import a single card credential per user as well as a license plate and entry code. To import more credentials, please use the import credential flow as described below.
{% endhint %}
***
## Import credential details and associated access user
When [Access Control Managers](/access-control/getting-started/roles-and-permissions-for-access-control.md) and Admins import credentials into Command in bulk with an uploaded .csv file, the file must contain a row for each credential to be imported, including the credential details and the access user that the credential should be associated with.
{% hint style="warning" %}
You can create new credentials or modify existing credentials for users who already exist in Command. To create new access users in Command, use [bulk access user import](/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system/import-access-control-users-csv.md).
{% endhint %}
### Format your .csv file
To achieve a successful import, we highly recommend that your .csv file **match the required format** below:
* The file should be a .csv file with UTF-8 encoding.
* The file size should not exceed 250,000 rows.
* Credentials are matched to existing users in Command, so you *cannot* create a user during the credential import process.
* One "key" column should be included in the import to map the user to an already existing user in Command. There are 3 "key" columns in hierarchical order:
* User ID
* External ID
* Email Address
* The import file CSV column headers should match the expected column headers, as defined in [column headers](#h_f385fad83f) below.
* Each row should contain a single unique credential. Avoid importing multiple credentials per row.
### Import credentials
Once you have formatted your file, you can import the credentials:
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}
{% step %}
**On the left navigation, click Access Users and Groups .**
{% endstep %}
{% step %}
**At the top right, click the Import dropdown and select Import Credentials.**
{% endstep %}
{% step %}
**When you enter the credential information, the Card Type should match the list of** [**supported card types**](https://docs.verkada.com/docs/access-control-supported-card-formats-datasheet.pdf)**, as listed under Accepted Formats.**
{% endstep %}
{% step %}
**On Import Credentials, you can download a template that includes formatted** [**column headers**](#h_f385fad83f) **and sample credential rows.**
{% endstep %}
{% step %}
**Drag and drop or upload the formatted .csv file for import.**
{% endstep %}
{% step %}
**(Optional) Choose to reassign credentials. An already-existing credential from Command is then reassigned to match the CSV file input.**
a. If you choose not to reassign a credential, the row shows an error if a duplicate credential is found (already assigned to an existing user).\
b. Only reassign credentials if you want your CSV file to be the source of truth.\
c. Click **Import Credentials.**
{% endstep %}
{% step %}
**Under Review Columns:**
a. If any errors are recognized in the columns, this page prompts you to review your file and fix the errors.\
b. Fix errors and re-upload the .csv file.\
c. Click **Next**.
{% endstep %}
{% step %}
**Under Review Rows:**
a. If any errors are recognized in the rows, this page prompts you to review your file and fix the errors.\
b. Fix errors and re-upload the .csv file.\
c. Click **Next**.
{% endstep %}
{% step %}
**Click Proceed with Import if no errors exist on the rows or columns. If you choose to ignore the review suggestions, the rows fail on the import.**
{% endstep %}
{% step %}
**After the import is complete:**
a. You should receive an **email** confirmation on the number of rows that passed and the number of rows that failed.\
b. You should receive a .csv file of the failed rows with a reason for the failure.\
c. Fix the failed rows and re-import these credentials to successfully import all desired credentials.
{% endstep %}
{% endstepper %}
***
## Export users and their corresponding credentials
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}
{% step %}
**On the left navigation, click Access Users and Groups .**
{% endstep %}
{% step %}
**At the top right, click Export and select Export Credentials.**
{% endstep %}
{% endstepper %}
A .csv file should export immediately where you can find it in your designated **Downloads** folder.
### Column headers for your file
Your .csv file contains the following credentials:
| | |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **User Credential** | **Description** |
| **First Name** | First name in Command. |
| **Last Name** | Last name in Command. |
| **User ID** | Verkada-managed unique ID associated with the user. |
| **External ID** | Customer-managed unique ID associated with the user. |
| **Employee ID** | Customer-managed ID associated with the user.
Note: Employee ID uniqueness is not enforced.
|
| **Email** | Email address associated with the user. |
| **Card Type** | Card type associated with the user. See [supported card formats](https://docs.verkada.com/docs/access-control-supported-card-formats-datasheet.pdf). |
| **Facility Code** | Facility code associated with the credential (if applicable). |
| **Card Number** | Numeric card number associated with the credential (if applicable). |
| **Card Number Hex** | Hexadecimal card number associated with the credential (if applicable). |
| **License Plate** | User license plate number (if applicable) is also listed as a credential for the user. |
| **Entry Code** | Unique access entry code (if applicable) is also listed as a credential for the user. |
| **Credential Status** | Verkada has introduced a Credential Status column.
If the credential is currently associated with a user, it is marked as an active credential.
If the credential is suspended, it is marked as inactive.
If a user is suspended, the credential is still active.
|
| **Modified** | Shows the date and time the credential was last updated. |
***
{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=8r7YcbrnGZY).
{% endhint %}
---
# Agent Instructions: 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/access-control/users-and-credentials/commission-access-control-cards/import-and-export-credentials-with-csv-files.md?ask=
```
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.