> For the complete documentation index, see [llms.txt](https://docs.nuvens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvens.cloud/admin/appendices/how-do-i-create-a-workspace-for-a-user/adding-a-single-new-user-and-creating-them-a-workspace.md).

# Adding a single new user and creating them a WorkSpace

In the WorkSpaces Manager dashboard, go to the Users section. You will see an option for ‘Add User’.

<figure><img src="https://1977539604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5qADNWBPym2Zh4ZaguCE%2Fuploads%2F9VnL6jsgPulk3gGw8BSR%2Fadduser.png?alt=media&amp;token=408bfa6b-dd70-4ddb-a128-2f938504ec61" alt=""><figcaption></figcaption></figure>

Fill in the user's details on the left—including name, email, username, and password. On the right, under WorkSpace Options, select the Account, Region, Directory, Mode, and Bundle you want applied to this user’s WorkSpace.

Once all required fields are complete, click Save. A confirmation message will appear to indicate that the WorkSpace is now being provisioned.

<figure><img src="https://1977539604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5qADNWBPym2Zh4ZaguCE%2Fuploads%2Far83AB26Ypo1a98EIRz6%2Fadduser2.png?alt=media&amp;token=7f3479e4-7903-47bf-849b-169d301b1df6" alt=""><figcaption></figcaption></figure>

The WorkSpace will take around 20-45 minutes to set up, depending on if it is to be encrypted. Nuvens always recommend encrypting both volumes. An email is automatically sent to the user with instructions on how to access their WorkSpace.


---

# 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.nuvens.cloud/admin/appendices/how-do-i-create-a-workspace-for-a-user/adding-a-single-new-user-and-creating-them-a-workspace.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.
