> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/managing-an-organization/organization-users/add-and-removing-users-from-your-organization.md).

# Add & removing users from your organization

* [#add-users-to-your-organization](#add-users-to-your-organization "mention")
* [#removing-users-from-your-organization](#removing-users-from-your-organization "mention")
* [#workspace-roles](#workspace-roles "mention")

### Add users to your Organization

To add new users to your **Organization**, go to *Users* within the Organization Overview and select *Add User*.

![Organization users](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2FTP7AIBQ68A9jKIgWBV5a%2Fscreely-1685008697892.png?alt=media\&token=4b7a089c-9d0e-4873-8ae0-12b46e999b35)

Add the user Email and select the appropriate user role:

{% hint style="info" %}
**Organization-Admins** can manage and edit the Organization and have full access to its Workspaces.

**Organization-Editors** have edit access to the Organization and its Workspaces.

**Organization-Viewers** have read-only access to the Organization and its Workspaces.
{% endhint %}

Adding a user requires at least **organization admin** rights.

### Removing users from your Organization

Users are removed from the same **Users** page. Removing a user takes away the organization role they were given, and with it the access to every workspace that role implied.

{% hint style="warning" %}
Removing an organization role does not necessarily remove the person from akenza. If they were also added to a workspace directly, that access survives, and they continue to appear in the list as **organization member**. To remove them entirely, also remove them from each [workspace](/device-management/managing-a-workspace/workspace-users.md) they belong to.
{% endhint %}

The [organization owner](/device-management/managing-an-organization/general-settings.md) cannot be removed. Transfer ownership to another member first.

### Workspace Roles

Organization roles and workspace roles are separate, and they meet in one direction only. An organization role above member carries an implicit role in **every** workspace of that organization, including workspaces created later. A workspace role grants access to that workspace alone and never extends up to the organization or across to its other workspaces.

Learn more about user roles:

{% content-ref url="/pages/-MVvnykxZJF8KQPqkfwZ" %}
[User Roles](/general/users/user-roles.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akenza.io/device-management/managing-an-organization/organization-users/add-and-removing-users-from-your-organization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.