> 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/users-and-credentials/verkada-pass-app/favorite-doors-in-verkada-pass-app.md).

# Favorite Doors in Pass App

Favorite your frequently used doors in the Verkada Pass App for easy access

The Verkada Pass app allows you to choose up to six favorite doors that you use most frequently. Favorited doors will appear at the top of your app, making it quicker and easier to unlock them when needed.

{% hint style="danger" %}
Favorite doors are currently only available on iOS. Verify your app is updated to the latest version from the [App Store](https://apps.apple.com/us/app/verkada-pass/id1477261074).
{% endhint %}

***

### Setup Favorite Doors

{% stepper %}
{% step %}
**Open the Verkada Pass app and select** <i class="fa-star">:star:</i>.
{% endstep %}

{% step %}
**Select the star next to each door you want to favorite.**
{% endstep %}

{% step %}
**Tap Done when finished.**
{% endstep %}
{% endstepper %}

Your selected favorite doors will appear at the top of the **Doors** list for easy access.


---

# 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/users-and-credentials/verkada-pass-app/favorite-doors-in-verkada-pass-app.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.