> 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/events-and-alerts/enable-mailroom-notifications.md).
# Enable Mailroom Notifications
Learn how to enable your Verkada Mailroom notifications
You can choose which notification types users receive when a package is ready for pickup. Supported notification methods include email, SMS, Slack, and Microsoft Teams.
{% hint style="danger" %}
You need **Org Admin** permissions to manage Mailroom settings.
{% endhint %}
***
## Configuration
{% stepper %}
{% step %}
**In Verkada Command, go to All Products Workplace > Mailroom.**
{% endstep %}
{% step %}
**On the left navigation, click Mailroom Settings.**
{% endstep %}
{% step %}
**Under Notifications, select the box next to the method you prefer for notifying your organization users (email, SMS, Slack, or Microsoft Teams).**
{% endstep %}
{% endstepper %}
***
## Edit user preferences
Once your Org Admin enables notifications, users can customize their preferred notification types at **my.verkada.com**.
{% stepper %}
{% step %}
**Go to** [**my.verkada.com**](https://my.verkada.com/)**.**
{% endstep %}
{% step %}
**Enter your email address to receive a login link.**
{% endstep %}
{% step %}
**In the email, click Go to my.verkada.com.**
{% endstep %}
{% step %}
**At the top right, click the menu (three vertical lines) icon and select Edit Profile.**
{% endstep %}
{% step %}
**Under I prefer to be contacted via…, choose your preferred contact methods.**
{% endstep %}
{% endstepper %}
***
## Package pickup notification
Once a package is delivered, users are:
* Notified through their selected contact methods (see examples below).
* Able to mark the package as **picked up**.
---
# 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/events-and-alerts/enable-mailroom-notifications.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.
