> For the complete documentation index, see [llms.txt](https://support.8seats.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.8seats.com/guides-for-8seats-admins/how-to-manage-roles-for-workspace-members.md).

# How to manage roles for Workspace members

Workspace owners and admins can update a member's role at any time from the Manage people & departments section.

1. In the left-hand navigation, select **Manage people & departments.**

<div align="left"><figure><img src="https://809702454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkSMdLZljqNqxCnK0AHoC%2Fuploads%2FKdnt536pJfoKK4iC6dYO%2FImage%203.png?alt=media&amp;token=cf951bf9-a3e9-45ef-9208-d1af1f6873a0" alt=""><figcaption></figcaption></figure></div>

2. Find the user you want to update and click **Edit.**
3. Scroll down to the Workspace role dropdown and select the appropriate role:

* **Owner** – full control of the workspace.
* **Admin** – can manage settings and users.
* **Member** – standard access.
* **Guest** – limited access.

<div align="left"><figure><img src="https://809702454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkSMdLZljqNqxCnK0AHoC%2Fuploads%2FfiqgiKRB1OkDtbFf9EYn%2FImage%204.png?alt=media&amp;token=f34e45c5-2160-4eec-9417-61f508327bb6" alt=""><figcaption></figcaption></figure></div>

4. Click **Save changes** once you have selected a Workspace role

{% hint style="info" %}
Note: You can sort my Workspace role in
{% endhint %}

<br>


---

# 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://support.8seats.com/guides-for-8seats-admins/how-to-manage-roles-for-workspace-members.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.
