> 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/de/erste-schritte/quick-reference-guide-for-verkada-access-control.md).

# Kurzanleitung für Verkada Zutrittskontrolle

Referenzlinks, die Ihnen bei der Navigation durch Ihre Verkada-Zutrittscontroller helfen

## Hardware-Installation

* [Datenblätter zur Zutrittskontrolle](https://www.verkada.com/docs/?product=accessControl\&contentType=datasheet)
* [Einrichtungsleitfäden zur Zutrittskontrolle](https://www.verkada.com/docs/?product=accessControl\&contentType=setupGuide)
* [Best Practices für die Bereitstellung der Zutrittskontrolle](/access-control/de/installation/access-control-deployment-best-practices.md)
* [Empfohlene Kabel für Zutrittscontroller](/access-control/de/installation/wire-a-door-to-a-verkada-access-controller/recommended-wires-for-access-controllers.md)
* [Eine Tür an einen Verkada-Zutrittscontroller verdrahten](/access-control/de/installation/wire-a-door-to-a-verkada-access-controller.md)

## Konfiguration und Einrichtung

* [Einen Zutrittscontroller zu Command hinzufügen](/access-control/de/konfiguration/add-an-access-controller-to-command.md)
* [Eine Tür zu einem Zutrittscontroller hinzufügen](/access-control/de/konfiguration/configure-a-door-in-command/add-a-door-to-an-access-controller.md)
* [Eine Tür in Command konfigurieren](/access-control/de/konfiguration/configure-a-door-in-command.md)
* [Einen Benutzer zum Verkada-Zutrittssystem hinzufügen](/access-control/de/benutzer-und-berechtigungsnachweise/add-a-user-to-the-verkada-access-system.md)
* [Besucherzugriff](/access-control/de/zutritt/visitor-access.md)
* [Zutrittsgruppen hinzufügen und ändern](/access-control/de/benutzer-und-berechtigungsnachweise/add-and-modify-access-groups.md)
* [Zutrittsstufen hinzufügen und ändern](/access-control/de/zutritt/add-and-modify-access-levels.md)
* [Unterstandorte der Zutrittskontrolle](/access-control/de/konfiguration/access-control-subsites.md)
* [Bluetooth-Entriegelung](/access-control/de/konfiguration/bluetooth-unlock.md)
* [Notfallverriegelung](/access-control/de/notfallreaktion/emergency-lockdown.md)

## Ereignisse und Warnmeldungen

* [Warnmeldungen für Zutrittskontrollereignisse konfigurieren](/access-control/de/integrationen-and-alarme/configure-access-control-event-alerts.md)
* [Warnmeldungen über alle Verkada-Produkte hinweg verwalten](/command/de/organisationseinstellungen/create-alerts-across-verkada-products/manage-alerts-across-verkada-products.md)

## Fehlerbehebung

* [Hardwareprüfungen der Zutrittskontrolle](/access-control/de/fehlerbehebung/access-control-hardware-checks.md)
* [Einen Zutrittscontroller neu starten](/access-control/de/fehlerbehebung/access-control-hardware-checks/restart-an-access-controller.md)
* [Fehlerbehebung bei sofortigem Wiederverriegeln der Tür](/access-control/de/fehlerbehebung/access-control-hardware-checks/troubleshoot-an-immediate-door-relock.md)
* [Offline-Betrieb von Verkada Access](/access-control/de/fehlerbehebung/access-control-hardware-checks/verkada-access-offline-operation.md)

{% hint style="info" %}
Folgen [unserem Blog](https://www.verkada.com/blog/) für alle unsere neuesten Funktionen und Ankündigungen!
{% endhint %}


---

# 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/de/erste-schritte/quick-reference-guide-for-verkada-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.