> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-add-users.md).

# How to Add Users

Add users to your organization, one by one or in bulk, with their details, password, and security.

Add the people who will work on the platform. You can do it one by one, with their profile and security settings in detail, or in bulk, importing several at once.

> #### 📘 **What will you get?**
>
> New users with access to the platform, with their data, language, password and two-step verification configured to your liking.

### Before you begin

You need to be logged in and have permission to manage users. The user is created from **Users**, and you have two options depending on where you are.

**From Home (your global view)** — in **Home > Users**, tab **My users**. This is the usual way when you work at a global level.

![Home > Users, with New user and Import users](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-3095a77e311bcef2a99623a60f550ca4312d43b8%2FUsers_-_N1.png?alt=media)

**From an organization** — in **Organization > Users**, with a selected organization. The user is created directly in that organization.

![Organization > Users, with the organization selected](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-542601fd3a79068fb62035c170b53b69a150c582%2FUsers_N3.png?alt=media)

In both cases the form is the same. What changes is the starting point.

### Individual sign-up

#### 1. Open the user creation form

In **Users**, click **New user**. The user registration form opens.

> 📘 If you enter from Home, the breadcrumb is **Home > Users > New user**.
>
> If you enter from an organization, it includes its name (for example, **Home > San Junipero > Users > New user**), because the user will remain in that organization.

#### 2. Enter the email

The first thing requested is the **email** of the user, which will be their login identifier. Enter it and click **Continue**.

![First step of sign-up: email](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-5dd970c6ebcb96c51ef5789a2ceaf730302ad6fa%2FEmail_Usuario.png?alt=media)

#### 3. Complete the general information

The form opens with the user's details:

* **Name** and **Surnames**.
* **Position** and **Phone** — optional.
* **Language** and **Time zone** — they adjust how the platform looks to them and how dates are displayed.

![User general information](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-72face19528695d8fdde9cf5119ce98da4b67cb3%2FCrear_Usuario.png?alt=media)

#### 4. Set the password

In **Password**, choose how it is set:

* **Enter a password manually** — you define it now, in the Password and Confirm password fields.
* **The user will set their own password** — they will be asked to create it on their first login.

#### 5. Enable two-step verification (optional)

Turn on the **Two-step verification** to add an extra layer of security to the login. It requires an authentication app, such as Google Authenticator, which the user will configure on their next login.

> #### 🚧 **Labels under review.**
>
> The two-step verification options are being refined in the dashboard.
>
> When you consult this guide, check the exact name of the switch.

#### 6. Register the user

Click **Register** to create them. The user will appear in the Users list.

#### 7. Assign their permissions

After registering them, the permissions screen opens **Permissions**, where you define what they can access: the dashboard, the organization sections, and each subscription. Permission assignment is explained step by step in [How to apply permissions to a user.](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md)

> #### 👍 **All green.**
>
> The user is created and, depending on what you chose, they will receive instructions to set their password or configure their two-step verification on first login.

### Bulk sign-up: import users

When you need to register several users at once:

1. In **Users**, click **Import users**.
2. Download the template offered by the dashboard.
3. Fill it in with the users' details and upload it to create them in bulk.

![Import users](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-8fda973905dd6e58c8b40867f9b88ccb034fb25b%2FImportar_usuarios.png?alt=media)

> #### 📘 **Always use the template.**
>
> The import expects the dashboard template format. Download it each time and fill it in as-is to avoid errors when uploading it.

### Conclusion

You now know how to add users to your organization: individually when you want to take care of each one's details, or in bulk when you register several at once. In both cases you define who has access, with what data and with what security.

### Next steps

* Learn how to edit, deactivate or delete them in [How to manage your users.](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-manage-users.md)
* See what each column in the list shows in [The lists.](https://docs.plenit.com/docs-en/platform/accounts/details/lists.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-add-users.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.
