> 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/mailroom/configuration/customize-your-mailroom-dashboard.md).
# Customize Your Mailroom Dashboard
Learn how to customize the Verkada Mailroom dashboard
Verkada Mailroom streamlines delivery management across all your facilities, ensuring inventory, supplies, and packages reach the right people on time. Each Mailroom site includes a customizable dashboard for tracking and managing deliveries.
***
## Switch between your Mailroom sites
To switch between your different Mailroom sites, click the dropdown at the top left corner and select a site.
***
## Search for packages
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Workplace > Mailroom.**
{% endstep %}
{% step %}
**In the left navigation, select Mailroom Home.**
{% endstep %}
{% step %}
**On the right, Mailroom Admins can:**
* Search for packages by **recipient name**, **location**, **carrier**, or **arrival/pickup date**.
* Switch between packages that are **waiting** or **picked up**.
{% endstep %}
{% endstepper %}
***
## Add context cameras
You can add up to 4 context cameras to a Mailroom site. It can be helpful to link cameras that cover areas, such as loading docks, lobbies, and package rooms.
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Workplace > Mailroom.**
{% endstep %}
{% step %}
**On the left navigation, select Mailroom Settings.**
{% endstep %}
{% step %}
**At the top, click Sites > your site.**
{% endstep %}
{% step %}
**Under Context Cameras, click Manage cameras.**
{% endstep %}
{% step %}
**Select up to 4 cameras that will appear at the top of the Mailroom site page. To clear the selected cameras (or existing cameras), click Clear.**
{% 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/mailroom/configuration/customize-your-mailroom-dashboard.md?ask=&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.
