> For the complete documentation index, see [llms.txt](https://help.visibrain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.visibrain.com/platform-guide/reports/email.md).

# Email

To receive and/or share your Reports by **Email**, you'll just need to click on Email and list all the email adresses you want to share this Report with.&#x20;

You can add as many email adresses as you want, you'll just need to click on the "+" sign to add a new one. The recipients of these Reports can be users of Visibrain or not, to delete an email adress from the list, just click on the "X" sign on the left.&#x20;

<figure><img src="/files/I4hh8QKiWvJFj9SKJzyT" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
We recommend you give clear and transparent titles to your Reports, it will help getting a better understanding of the Report you are reading.&#x20;
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.visibrain.com/platform-guide/reports/email.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
