> For the complete documentation index, see [llms.txt](https://docs.nexos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexos.ai/workspace/settings/organization/users.md).
# Users
Users is where organization admins manage who can access your nexos.ai workspace. From here, you can invite people, update access, and remove users who no longer need access.
At the top of the Users page, you can see the total number of users in your organization and how many seats are still available. You can also use the search bar and filters (such as Teams, Role, and Status) to quickly narrow down the list and find specific users faster.
## How to use it
{% stepper %}
{% step %}
### Open Users
Open Settings, then go to Organization > Users.
{% endstep %}
{% step %}
### Invite users
On the Users page, select Invite users.
Enter one or more email addresses, then send the invite.
If your organization uses teams or roles, choose the correct access options before sending.
{% endstep %}
{% step %}
### Update a user’s access
Find the user you want to update.
Select the user’s **Role** or **Team** next to their name, then choose the new value from the menu that opens.
{% endstep %}
{% step %}
### Remove a user
Find the user you want to remove.
Open the user actions menu and select Remove.
Confirm to revoke access to your organization.
{% endstep %}
{% endstepper %}
Use Users when you are onboarding teammates, changing responsibilities, or offboarding people who should no longer have access.
---
# 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.nexos.ai/workspace/settings/organization/users.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.
