> 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.md).

# Organization Users

Add and remove users at organization level, and assign organization roles.

The **Users** page of an organization lists everyone with access to it and the role they hold. Access granted here reaches the organization and **every** workspace in it, including workspaces created later, which makes it the right level for people who work across the whole account. For access to a single project or site, use [Workspace Users](/device-management/managing-a-workspace/workspace-users.md) instead.

{% content-ref url="/pages/2jrXgXOtAj7QPMD4wIMc" %}
[Users](/general/users.md)
{% endcontent-ref %}

## Roles

<table><thead><tr><th width="250">Role</th><th>Access</th></tr></thead><tbody><tr><td><strong>Organization owner</strong></td><td>The single user who owns the organization. Only the owner can delete it or transfer ownership.</td></tr><tr><td><strong>Organization admin</strong></td><td>Can manage and edit the organization, including its users and billing, with full access to its workspaces.</td></tr><tr><td><strong>Organization editor</strong></td><td>Edit access to the organization and its workspaces, but cannot add or remove users.</td></tr><tr><td><strong>Organization viewer</strong></td><td>Read-only access to the organization and its workspaces.</td></tr><tr><td><strong>Organization member</strong></td><td>Reaches the organization only through the workspaces they belong to.</td></tr></tbody></table>

{% hint style="info" %}
A user with access to at least one workspace in the organization appears here as **organization member**, even though they were never added at organization level. That is the role's purpose: it records their presence without granting organization-wide access.
{% endhint %}

Managing users requires the **organization owner** or **admin** role. For the full breakdown of what each role permits, see the [permission matrix](/general/users/user-roles.md).

{% content-ref url="/pages/mk4TxkSxPtPKABDFycdi" %}
[Add & removing users from your organization](/device-management/managing-an-organization/organization-users/add-and-removing-users-from-your-organization.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.akenza.io/device-management/managing-an-organization/organization-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.