> 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/ko/integrations-and-alerts.md).

# 통합 및 알림

- [출입 이벤트 알림 구성](https://help.verkada.com/access-control/ko/integrations-and-alerts/configure-access-control-event-alerts.md): 출입 통제 이벤트에 대한 알림을 구성하고 활성화하는 방법을 알아보세요
- [동반 진입 감지](https://help.verkada.com/access-control/ko/integrations-and-alerts/configure-access-control-event-alerts/access-control-tailgate-detection.md): 출입 통제 동반 진입 감지를 활성화하고 구성하는 방법을 알아보세요
- [출입 통제 보고서](https://help.verkada.com/access-control/ko/integrations-and-alerts/access-control-reports.md): 보고서를 사용하면 출입 통제 이벤트를 쉽게 보고 내보낼 수 있습니다
- [근태 분석](https://help.verkada.com/access-control/ko/integrations-and-alerts/access-control-reports/attendance-analytics.md): 출입 데이터를 활용하여 직장 사용 및 직원 출근 추세를 파악하세요
- [InformaCast 통합](https://help.verkada.com/access-control/ko/integrations-and-alerts/informacast-access-control-integration.md): Verkada Command를 Singlewire InformaCast와 통합하는 방법을 알아보세요
- [Atrium과의 Verkada 통합](https://help.verkada.com/access-control/ko/integrations-and-alerts/verkada-integration-with-atrium.md)
- [Suprema BioStation3 리더](https://help.verkada.com/access-control/ko/integrations-and-alerts/integrate-supremas-biostation3-readers-with-verkada-access-control.md)
- [출입 사용자로부터 관심 인물 생성](https://help.verkada.com/access-control/ko/integrations-and-alerts/create-a-person-of-interest-from-an-access-user.md): 기존 출입 사용자로부터 POI를 만드는 방법을 알아보세요
- [장치 간 로컬 연결](https://help.verkada.com/access-control/ko/integrations-and-alerts/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/ko/integrations-and-alerts/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/ko/integrations-and-alerts.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.