> For the complete documentation index, see [llms.txt](https://docs.zmanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zmanda.com/start-here/step-1-adding-a-user.md).

# Step 1: Adding a User

{% hint style="info" %}
To ensure maximum security and optimal performance, you should create a unique user for each device you onboard. We provide [bulk automation scripts](https://docs.zmanda.com/automation-tools/bulk-operations-with-zpat) that allow you to automatically create users, install agents, register devices, and configure backup jobs for ***thousands*** of devices at once with just minutes of administrative work. For more information, see the hyperlinked article above, or contact us at [sales@zmanda.com](https://www.zmanda.com/contact-sales/)
{% endhint %}

Backup user profiles play a crucial role in encryption and key management, serving as a security boundary. It is impossible to decrypt backups without the corresponding user credentials.

User profiles include other configurations such as client timezone and language settings, 2FA for end-users, and email reporting.

### Video Tutorial

{% embed url="<https://youtu.be/1-U7YLt0tdc?si=vyRFlM49CcqnubHr>" %}

### Adding a Single User

Click the **Add User** button on the Dashboard or within the Users tab.

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

A pop-up will appear. Fill in the necessary fields as prompted.

* **Account Name** - Optional field to help organize groups of related users
* **Username** - Required
* **Password** - The password used to encrypt the encryption keys for the backup data
* **Email** - An optional email address where job reports can be sent (if configured)
* **Storage** - Optional field that automatically provisions a storage vault for the user using a storage template
* **Apply Policy** - An optional policy that templatizes the configuration of backup jobs, scheduling, retention policies, etc.
* **Allow administrator to reset password** - Recommended to leave this enabled
* **Require user to change password at next login** - Recommended to disable this unless an end user requires access to run backup/restore jobs

{% hint style="warning" %}
If you deselect the **Allow administrator to reset password** box, the zero-trust security model will be enabled and you will be required to securely store (or remember) the user's password to restore backups. For more information, [see this article](https://kb.zmanda.com/zmanda-pro-zero-trust-model).
{% endhint %}

<figure><img src="/files/1FKstQ5zaflvdV5u7riF" alt=""><figcaption></figcaption></figure>

After adding a new user, you will be redirected to the user's account page.

### Adding Multiple Users

You may optionally add multiple users at a time by pasting in the account name, username, password, and email in CSV format:

{% hint style="info" %}
RECOMMENDED: Users can also be added automatically and in bulk using our [automation scripts](https://docs.zmanda.com/automation-tools/bulk-operations-with-zpat).
{% endhint %}

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


---

# 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.zmanda.com/start-here/step-1-adding-a-user.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.