> 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/multi-factor-authentication-mfa-codes/enable-two-factor-entry-with-access-control.md).

# Enable Two-Factor Entry

Learn how to unlock a door with 2FA requirement

To add additional security to a door, you can require both a key card and an entry code to gain access. You can only add this type of two-factor authentication (2FA) to doors that include both a badge reader and a keypad.

{% hint style="danger" %}

* You must have *both* a key card and an entry code configured on your [access profile](/access-control/users-and-credentials/add-a-user-to-the-verkada-access-system.md) to access any door configured for two-factor entry.
* When unlocking a door, the card or fob must be scanned on the reader *before* the PIN code is entered, followed by **#** to submit (for example, **1234#**).
* In the Pass app, Bluetooth Unlock does not function in the same way as a keycard and cannot unlock the door by itself. However, NFC does function as a keycard and can unlock the door when used with a PIN code. Additionally, both Nearby and Remote Unlocks will still unlock the door without requiring a code.
* If you have an In/Out door two-factor entry will only be required when entering the door.
* You **must** be an Access Site Admin of at least one site with an access controller in it to view the access controllers option on the **Devices** page. See [Roles and Permissions for Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md) for more information.
  {% endhint %}

***

## Enable two-factor entry on a door schedule

{% hint style="danger" %}
You must [create a door schedule](/access-control/access/door-schedules-and-exceptions.md) if you have not done so already.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}

{% step %}
**On the left navigation, click Schedules .**
{% endstep %}

{% step %}
**Select Door Schedules.**
{% endstep %}

{% step %}
**Select the schedule to which you want to add two-factor entry.**
{% endstep %}

{% step %}
**Select the day on the schedule you want to enable this feature and configure these settings as needed:**

a. **Two-factor entry** status.\
b. Start and end times for the schedule.\
c. Days the schedule repeats on.\
d. Click **Done** when finished.
{% endstep %}

{% step %}
**Click Save.**
{% endstep %}
{% endstepper %}

***

## Enable two-factor entry on a door exception

{% hint style="danger" %}
You must [create a door exception](/access-control/access/door-schedules-and-exceptions.md) if you have not done so already.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}

{% step %}
**On the left navigation, click Schedules .**
{% endstep %}

{% step %}
**Select Door Exceptions.**
{% endstep %}

{% step %}
**Select the exception to which you want to add two-factor entry.**
{% endstep %}

{% step %}
**Select the day on the schedule you want to enable this feature and configure these settings as needed:**

a. **Two-Factor Entry Door** status.\
b. Start and end times for the schedule.\
c. Days the schedule repeats on.\
d. Click **Done** when finished.
{% endstep %}

{% step %}
**Click Save.**
{% endstep %}
{% endstepper %}

***

## Troubleshooting

A common issue with two-factor entry is that one of the authentication methods fails. To troubleshoot this, temporarily disable **Two-Factor Entry** for **Access Controlled** until it is confirmed that both the key card and entry code can individually grant access to the door.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/access-control/users-and-credentials/multi-factor-authentication-mfa-codes/enable-two-factor-entry-with-access-control.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.