> For the complete documentation index, see [llms.txt](https://docs.emaildelivery.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emaildelivery.com/docs/backend-administration/creating-user-accounts.md).

# Creating User accounts

{% hint style="info" %}
**User accounts log in to the email marketing frontend**

A user account logs in directly to the frontend with an email address and password, a user account does not have access to the backend.
{% endhint %}

{% hint style="warning" %}
**User accounts share a customer account**

A user account is a sub-user of a customer account, all user accounts share access to all of the customer account's data and are not siloed, *user accounts are not an isolated environment.*&#x20;
{% endhint %}

{% hint style="info" %}
**Customer accounts do not share data or users**

In contrast to user accounts, customer accounts are siloed, each customer account is an isolated environment.
{% endhint %}

**Click Customers -> Customer Accounts**

<div align="left"><figure><img src="/files/CdfexL7ABMcNr6GkM2NI" alt="" width="368"><figcaption></figcaption></figure></div>

**Click the customer account you want to create an email marketing user account under:**

<div align="left"><figure><img src="/files/fCrVEsFmwT37LDp0XPTP" alt="" width="135"><figcaption></figcaption></figure></div>

**Alternatively you can use edit from the action menu:**

<div align="left"><figure><img src="/files/miPng9Qwd8cr5MEG6cCX" alt="" width="188"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Creating your first user**

Your platform ships with a default customer account named Acme Co without any users, by creating a user account you can log directly into the email marketing frontend with a unique username/password combination.
{% endhint %}

**Click the&#x20;*****users tab*****&#x20;and Create User:**

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

{% hint style="info" %}
**Email address and name**

The user account email address doesn't need to actually exist, you can use anything you want here. However, the email address and name entered will be filled in as the default when you create a new email marketing broadcast, where they can always be modified.&#x20;
{% endhint %}

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

{% hint style="info" %}
**No data export allowed**

Checking this box prevents this user account from being able to download contact list data from the email marketing frontend.
{% endhint %}

{% hint style="info" %}
**Disabled**

Checking this box will temporarily disable a user account without deleting it.
{% endhint %}

**Remember to save!**

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

{% hint style="info" %}
**Log in with user accounts at the same admin\_url URL as your backend admin account**

Backend admin accounts and email marketing frontend users access the platform at the same admin\_url login page. Admin users will be automatically logged in to the backend, user accounts will be automatically logged in to the frontend.&#x20;
{% endhint %}

{% hint style="info" %}
To stay logged in as the backend admin while logging in as an email marketing user account on the frontend use an incognito window, another browser, or Firefox containers.&#x20;

Alternatively, you can use customer account impersonation to open the email marketing frontend in a new tab while staying logged in as the backend admin. &#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://docs.emaildelivery.com/docs/backend-administration/creating-user-accounts.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.
