2021-05-18 11:19:33 +02:00
---
2022-01-14 13:08:04 +01:00
title: How to add new users to your Unleash instance
2021-05-18 11:19:33 +02:00
---
> This feature was introduced in Unleash v4 for Unleash Open-Source.
2022-01-14 13:08:04 +01:00
You can add new users to Unleash in `Admin > Users` .
2021-05-18 11:19:33 +02:00
2022-01-14 13:08:04 +01:00
1. From the top-line menu – click on the “Settings Wheel” then click on “Users”.
![A visual representation of the current step: the Unleash Admin UI with the steps highlighted. ](/img/user_admin_list_button.png )
2021-09-21 17:21:48 +02:00
2022-09-14 09:59:18 +02:00
2. To add a new user to your Unleash instance, use the "new user" button:
2022-01-14 13:08:04 +01:00
![The Unleash users page with the 'add new user' button being pointed to. ](/img/user_admin-add-user.jpg )
2021-09-21 17:21:48 +02:00
refactor: move docs into new structure / fix links for SEO (#2416)
## What
This (admittedly massive) PR updates the "physical" documentation
structure and fixes url inconsistencies and SEO problems reported by
marketing. The main points are:
- remove or move directories : advanced, user_guide, deploy, api
- move the files contained within to the appropriate one of topics,
how-to, tutorials, or reference
- update internal doc links and product links to the content
- create client-side redirects for all the urls that have changed.
A number of the files have been renamed in small ways to better match
their url and to make them easier to find. Additionally, the top-level
api directory has been moved to /reference/api/legacy/unleash (see the
discussion points section for more on this).
## Why
When moving our doc structure to diataxis a while back, we left the
"physical' files lying where they were, because it didn't matter much to
the new structure. However, that did introduce some inconsistencies with
where you place docs and how we organize them.
There's also the discrepancies in whether urls us underscores or hyphens
(which isn't necessarily the same as their file name), which has been
annoying me for a while, but now has also been raised by marketing as an
issue in terms of SEO.
## Discussion points
The old, hand-written API docs have been moved from /api to
/reference/api/legacy/unleash. There _is_ a /reference/api/unleash
directory, but this is being populated by the OpenAPI plugin, and mixing
those could only cause trouble. However, I'm unsure about putting
/legacy/ in the title, because the API isn't legacy, the docs are. Maybe
we could use another path? Like /old-docs/ or something? I'd appreciate
some input on this.
2022-11-22 10:05:30 +01:00
3. Fill out the required fields in the "create user" form. Refer to the [global roles overview ](../reference/rbac.md#standard-roles ) for more information on roles.
2021-09-21 17:21:48 +02:00
2022-01-14 13:08:04 +01:00
![A form titled "Add team member". It has the fields "full name", "email", and "role". The role field is a radio button set with roles called "admin", "editor", and "viewer". ](/img/user_admin_add_user_modal.png )
2021-05-18 11:19:33 +02:00
2022-01-14 13:08:04 +01:00
If you have configured an email server the user will receive the invite link in her inbox, otherwise you should share the magic invite link to Unleash presented in the confirmation dialogue.