> 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/ja/she-ding/access-station-pro-end-to-end-setup-guide/face-unlock-setup/access-station-pro-2fa-setup.md).

# 顔認証解錠による 2 要素認証

Access Station Pro（AF64）で顔認証解錠を使った 2 要素認証（2FA）を設定する

Face Unlock を使用して2要素認証（2FA）を設定し、ドアアクセスに追加のセキュリティ層を追加します。

### 始める前に

* [ドアに2要素エントリのスケジュールを適用する](/access-control/ja/akusesu/door-schedules-and-exceptions.md)
* [ドアでTwo-Factor（2FA）Entry設定を構成する](/access-control/ja/yzto/multi-factor-authentication-mfa-codes/enable-two-factor-entry-with-access-control.md)

***

## 設定

{% stepper %}
{% step %}
**Verkada Command で、All Products > Access に移動します。**
{% endstep %}

{% step %}
**Two-Factor Entry を適用したい AF64 で制御されるドアを選択します。**
{% endstep %}

{% step %}
**上部で、［設定］を選択します。**
{% endstep %}

{% step %}
**［ドア］>［インストーラー設定］で、［Two-Factor（2FA）Entry］の横にある［管理］をクリックします。**
{% endstep %}

{% step %}
**ドアで許可する認証情報の組み合わせを選択します**.

* カード + コード
* 顔 + カード
* 顔 + コード

{% hint style="danger" %}

* Face Unlock が無効になっている場合、顔の提示が必要な組み合わせは機能しません。
* Face Unlock を含む組み合わせでは、ユーザーは最初に顔を提示する必要があります。
* カード + コードまたは顔 + コードのようにエントリーコードを必要とする組み合わせでは、ユーザーは AF64 のタッチスクリーンキーパッドでコードを入力し、その後に **#** 送信するには（例： **1234#**）。詳細は [Two-Factor Entry を有効にする](/access-control/ja/yzto/multi-factor-authentication-mfa-codes/enable-two-factor-entry-with-access-control.md) 詳細については
  {% endhint %}
  {% endstep %}
  {% endstepper %}


---

# 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/ja/she-ding/access-station-pro-end-to-end-setup-guide/face-unlock-setup/access-station-pro-2fa-setup.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.