> 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.md). # Users and roles Add team members to your Navixy account, decide what each can do with roles, and choose which objects, POI, and geofences each can see. One person rarely runs a fleet. Dispatchers, regional managers, and accountants all need Navixy, but each of them needs different data and different tools. With **Users and roles**, the account owner gives each team member their own sign-in and access to only the data and actions that they need. For example, you can: * Give the dispatcher of a regional branch the vehicles, depots, and delivery zones of that branch only. * Let an accountant make payments and view transactions, without access to device settings. * Check what a user sees by opening their account without their password. The access of each user has two parts: * The [role](/docs/user/guide/account/users-and-roles/role-management.md) decides what the user can do: change device settings, edit geofences, build reports, and so on. One role applies to many users. * The [assigned items](/docs/user/guide/account/users-and-roles/restricting-access.md) decide which objects (GPS devices), POI, and geofences the user sees. You choose them for each user. Only the account owner can add users and change their access. **Users and roles** is available when the tariff plan of every device in the account includes it. ## Where to start * [Restricting access](/docs/user/guide/account/users-and-roles/restricting-access.md): Choose which objects, POI, and geofences each user can see. * [User administration](/docs/user/guide/account/users-and-roles/user-administration.md): Add, edit, deactivate, and delete users. * [Roles](/docs/user/guide/account/users-and-roles/role-management.md): Learn what each right allows and how to limit the history that users can view. --- # 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.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.