> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/user-guide/add-remove-users.md).

# How Do I Remove or Add a User?

To remove or invite new users to your Archera account, navigate to the arrow in the top left next to your org name. Then click on "Organization Settings" followed by clicking on the "Users" section.

## Adding Users

To add users, click the **"Invite Members"** button at the top of the page to invite a new user via their email and assign a specific role.

## Managing and Removing Users

To manage or remove specific users, you can click the remove button to revoke access or change the user's role in the table.

## Restricting Cloud Access

If you would like to opt-out of giving your cloud account representatives or MSP/Reseller/Cloud-Consultants access to your environment, you can restrict their role or remove them from your account entirely via this page.

## Related Resources

* [Invite Users and Onboarding Troubleshooting](/help-center/user-guide/invite-users.md)
* [Settings & Integrations - Section Overview](/help-center/user-guide/settings-integrations.md)


---

# 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.archera.ai/help-center/user-guide/add-remove-users.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.