> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/mails.md).

# Mails

In this overview, you can adjust various settings related to the emails in the system.

### System mail templates

Here, you can modify various email templates that are sent from our system. By clicking on the pencil icon next to the relevant email, the editor will open, allowing you to customize the email as desired.

### My mail templates

In this overview, you will find emails that you have previously sent. If the environment was copied from a past event, the emails you previously set up will also be included. This can save a lot of time when setting up or adjusting emails. If you have organized multiple events and copied them repeatedly, this list may become quite extensive. Therefore, it is also possible to delete personal email templates from this overview, as long as they are not linked to an outstanding email in the current environment.

### Session host instructions

For more information about session host instructions, you can refer to [this](#session-host-instructions) article. 


---

# 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://knowledge-base.letsgetdigital.com/the-admin-panel/settings/mails.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.