> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/other/email/how-tos/create-an-email-account.md).

# Create an email account

***

## Preparations

You find the email service via the **Email** button in the left-hand menu under **Domains**.

The email service is closely integrated with the DNS service. To create an email account, you first need a domain in the DNS service. However, note that you do not need to use Glesys DNS or Glesys as the registrar for the domain name. You only need to add the domain to the DNS service.

All domains added to the project's DNS service are also available in the email service. If you do not see any domains in the email service, two buttons are displayed instead: **Register domain** and **Add or transfer existing domain**. Both of these buttons take us to the DNS service. Refer to the [DNS documentation](/products/connectivity/domains-and-dns.md) for instructions on how to add or register domain names in the Glesys DNS service.

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

When you have one or more domains registered in the DNS service, you can select these for the email service. In the overview, you can see how many email accounts and aliases exist under each domain.

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

{% hint style="warning" %}
To be able to receive emails to Glesys you also need to add Glesys mail servers to the DNS. Add the servers as MX records. See [Configure the DNS for Glesys email](/products/other/email/how-tos/configure-the-dns-for-glesys-email.md) on how to do this.
{% endhint %}

## Create new email accounts using the control panel

Via the email service's overview, click on the domain name under which you want to create new email accounts.

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

Now you can choose to create new email accounts under the domain. Click on the plus sign in the upper right corner and then on **Create account** to create a new account.

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

In the dialog box that opens, enter a name for the recipient. This is the name that appears before the @ symbol. Then, click on **Create**.

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

The password for the email account is now displayed. You must save this in a secure location. It cannot be displayed again. If you forget it, you will need to create a new password. Once you have noted down the password, click on **Close**.

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

The email account is now ready and is visible in the overview for the specific domain name in the email service.

## Create new email accounts using the API

Use the [email/createaccount](https://github.com/GleSYS/API-docs/wiki/API-Documentation#emailcreateaccount) endpoint to create new email accounts using the [API](/platform/control-panel/api.md).


---

# 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:

```
GET https://docs.glesys.com/products/other/email/how-tos/create-an-email-account.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
