> 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.md).

# Access Station Pro の概要

AF64 Access Station Pro を始めるために必要なすべて

AF64 Access Station Pro は、マルチテクノロジーリーダー、1ドアコントローラー、PIN入力に使用できる 5.5 インチの応答性の高いタッチスクリーン、そして高機能な 500万画素の広角カメラを 1 台に統合し、PoE 給電で動作するデバイスとして、エントランス全体のセキュリティを実現します。

また、Face Unlock も搭載しています。これは、近づいて見つめるだけでデバイスのロックを解除できるアクセス方法です。Face Unlock は、ユーザーの本人確認に顔認識技術を使用し、赤外線 3D センサーで、許可されたユーザーの写真やマスクを使ってアクセスしようとするなりすましの試みを防ぎます。

***

## Access Station Pro の導入手順

{% stepper %}
{% step %}
**Access Station Pro をドアに取り付けます。**

* 参照してください [Access Station Pro の設置](/access-control/ja/insutru/access-station-pro-installation-and-mounting.md) で配置の概要をご確認ください。
* 手順ごとの設置手順については、 [Verkada AF64（Access Station Pro）インストールガイド](https://docs.verkada.com/docs/af64-access-station-pro-install-guide.pdf).
  {% endstep %}

{% step %}
**Access Station Pro を Command に追加し、ドアとカメラの設定を構成します。**

参照 [Access Station Pro Command の設定](/access-control/ja/she-ding/access-station-pro-end-to-end-setup-guide/access-station-pro-command-configuration.md) を参照してください。
{% endstep %}

{% step %}
**（オプション）ドアで Face Unlock アクセスを設定します。**

参照 [顔認証解除](/access-control/ja/readme.md) 詳細については
{% 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.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.