> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/account/users-and-roles/user-administration.md).
# User administration
Give each team member their own sign-in to your Navixy account. Add, edit, deactivate, and delete users, and check what each user sees.
User administration lets the account owner give each team member their own sign-in to the Navixy account. Dispatchers, managers, accountants, and contractors work in one account, each with their own tools and data. The owner keeps full control over who sees and does what.
Each user gets two kinds of limits:
* A [role](/docs/user/guide/account/users-and-roles/role-management.md) decides what the user can do, for example, change device settings or build reports.
* [Assigned items](/docs/user/guide/account/users-and-roles/restricting-access.md) decide which objects, POI, and geofences the user can see.
{% hint style="info" %}
**Navigation**
Click your account name at the top of the sidebar, then click **Users and roles**. The **User administration** tab opens. Only the account owner can open this screen.
{% endhint %}
The Users list, grouped by role, and the items assigned to the selected user.
## Owner and users
The owner is the main account holder. The owner sees every item in the account, has every right, and is the only one who can manage users. You can't deactivate, delete, or restrict the owner.
A user signs in with their own email and password. The user sees only the items that the owner assigns and does only what their role allows.
## How to add a user
To add a user, follow these steps:
1. On the **User administration** tab, click **+**.
2. Enter the **First name**, **Email**, and **Password** of the user. The password needs at least 6 characters.
3. In **Role**, select the role that the user needs. Navixy selects the default role for you.
4. Click **Save**.
The New user form. First name, Email, and Password are required.
Give the user the email and password that you entered. Then choose what the user can see: a new user sees no objects, but all POI and geofences. See [Restricting access](/docs/user/guide/account/users-and-roles/restricting-access.md).
## Managing users
Point to a user in the list to see the quick actions:
* **Log in as user**: Open the account of the user without their password and check what they see. To go back, click **Return to master account**.
* **Change password**: Set a new password for the user.
* **Edit**: Change the name, email, phone, or role of the user.
* **Delete**: Delete the user.
To change the role or the status of several users at once, select them and click **Change role** or **Change status** in the toolbar.
## How to deactivate or delete a user
To stop a user from signing in, turn off their **Activation** switch. The role and assigned items of the user stay, and they work again when you turn the switch back on.
{% hint style="danger" %}
You can't restore a deleted user. Navixy deletes the reports of the user and the rules that they hid from other users. Everything else that they created stays in your account: objects that they activated, other rules, POI, geofences, employees, vehicles, and tasks.
{% endhint %}
## See also
* [Restricting access](/docs/user/guide/account/users-and-roles/restricting-access.md): Choose which objects, POI, and geofences each user can see.
* [Roles](/docs/user/guide/account/users-and-roles/role-management.md): Learn what each right allows and how far back a user can view history.
---
# 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://navixy.com/docs/user/guide/account/users-and-roles/user-administration.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.
