> 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-a-workspace/workspace-users.md).

# Workspace Users

Grant access to a single workspace and assign workspace roles.

The **Users** page of a workspace lists everyone who can reach it and the role they hold. Access granted here applies to this workspace alone, which makes it the right level for a customer, a contractor, or a team responsible for one site. For access across every workspace at once, use [Organization Users](/device-management/managing-an-organization/organization-users.md) instead.

## Add users to your Workspace

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

![Workspace users](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2Fg32sCXipCjSK9alZFgPg%2Fscreely-1685008973131.png?alt=media\&token=e3d2a908-da36-4119-a614-0ea69655d356)

Add the user Email and select the appropriate user role:

{% hint style="info" %}
**Workspace-Admins** have full access on the Workspace.

**Workspace-Editors** have edit access on the Workspace.

**Workspace-Viewers** have read-only access on the Workspace.
{% endhint %}

Adding, removing, and re-assigning users requires the **workspace admin** role, or an organization admin or owner. Workspace editors can change the contents of a workspace but not who may reach it.

## Removing users from a workspace

Users are removed from the same **Users** page. Removing someone takes away their access to this workspace only.

{% hint style="warning" %}
If the person also holds an organization role above member, they keep access to this workspace through that role, and removing them here changes nothing. In that case the role has to be changed at [organization level](/device-management/managing-an-organization/organization-users.md).
{% endhint %}

## Organization users in this list

The user list shows both the organization role and the workspace role for each person, because the two combine. Anyone with an organization role above member already has access to this workspace without ever being added to it.

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

{% 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 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-a-workspace/workspace-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.