> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/helm/manage-vulnerabilities/identify-and-prioritize-exploitable-vulnerabilities/get-email-notifications-for-new-vulnerabilities.md).

# Get email notifications for new vulnerabilities

Stay on top of the latest vulnerabilities to impact your sofware supply chain. You can choose to receive daily, weekly, and/or monthly digests. These alerts ensure that you stay updated on potential risks and can take prioritize and mitigate risk promptly.

### Manage email preferences

1. Click on your **user avatar** located in the top navigation area of Helm.
2. Select **My profile** from the dropdown menu.
3. Toggle on the **Send me vulnerability email digests** switch if it's not already on.
4. Check one or more frequencies.
5. If you prefer not to receive email alerts, toggle off the **Send me vulnerability email digests** switch.
6. Click **Save**.

### When to expect vulnerability emails

* **Daily:** You’ll receive your first daily vulnerability email on the next business day.
* **Weekly:** You’ll receive your first weekly vulnerability email on the next Monday.
* **Monthly:** You’ll receive your first monthly vulnerability email on the 1st of every month.


---

# 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://docs.medcrypt.com/medcrypt-documentation/helm/manage-vulnerabilities/identify-and-prioritize-exploitable-vulnerabilities/get-email-notifications-for-new-vulnerabilities.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.