> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/organization-and-account-settings/users-and-roles/add-new-user.md).
# Add new user
{% hint style="success" %}
**Access Type**: Admin
{% endhint %}
Users added to your organization will be able to perform actions within your account based on the role assigned to that user. In this article, we will cover how to add a new user to your organization.
Click **My Organization** and select **Users & Roles** from the drop-down menu.
Click **Invite a user +** on the subsequent page.
Use the modal to input the following for the new user:
* Email Address
* Name
* Role
{% hint style="info" %}
Users can only be assigned one role within your organization. [Click here](/organization-and-account-settings/users-and-roles/create-new-role.md) to learn more about creating and managing roles.
{% endhint %}
Click **Send Invitation** when finished.
An automated email will be delivered to the new user which will enable to create a user account.
---
# 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.didomi.io/organization-and-account-settings/users-and-roles/add-new-user.md?ask=&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.
