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

# 連携とアラート

- [アクセスイベントアラートを設定する](https://help.verkada.com/access-control/ja/toarto/configure-access-control-event-alerts.md): アクセスコントロールイベントのアラートを設定して有効にする方法を学ぶ
- [テールゲート検出](https://help.verkada.com/access-control/ja/toarto/configure-access-control-event-alerts/access-control-tailgate-detection.md): アクセスコントロールのテールゲート検出を有効化して設定する方法を学ぶ
- [アクセスコントロールレポート](https://help.verkada.com/access-control/ja/toarto/access-control-reports.md): レポートを使ってアクセスコントロールイベントを簡単に表示・エクスポートできます
- [出席分析](https://help.verkada.com/access-control/ja/toarto/access-control-reports/attendance-analytics.md): アクセスデータを活用して、職場での利用状況や従業員の出勤傾向を把握する
- [InformaCast 連携](https://help.verkada.com/access-control/ja/toarto/informacast-access-control-integration.md): Verkada Command と Singlewire InformaCast を連携する方法を学ぶ
- [Atrium との Verkada 連携](https://help.verkada.com/access-control/ja/toarto/verkada-integration-with-atrium.md)
- [Suprema BioStation3 リーダー](https://help.verkada.com/access-control/ja/toarto/integrate-supremas-biostation3-readers-with-verkada-access-control.md)
- [アクセスユーザーから登録人物を作成する](https://help.verkada.com/access-control/ja/toarto/create-a-person-of-interest-from-an-access-user.md): 既存のアクセスコントロールユーザーから登録人物（POI）を作成する方法を学ぶ
- [デバイス間のローカル接続](https://help.verkada.com/access-control/ja/toarto/create-a-person-of-interest-from-an-access-user/cross-device-local-connections-for-access-control.md): アクセスコントローラが LAN 経由で他の Verkada デバイスと直接通信する仕組み
- [API でドアを管理する](https://help.verkada.com/access-control/ja/toarto/manage-doors-via-api.md): サードパーティプラットフォームで Verkada のアクセスコントロール対象ドアを管理する


---

# 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/toarto.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.