> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/account-and-team/users-and-roles/how-to-change-a-users-role.md).

# How to change a user's role

Change what someone can do in your account or workspace by opening their row in the user list and picking a new role from the dropdown. The roles are **Admin**, **Editor**, and **Viewer**, and the steps are the same wherever you manage users.

{% hint style="warning" icon="list-check" %}

#### Prerequisites

You need Admin permissions at the level where you're changing the role. Editors can't manage users.
{% endhint %}

#### How to change a user's role

{% stepper %}
{% step %}
**Open the user list**

For account-wide access, go to **Account settings** and click the **Users** tab. For a single workspace, go to **Workspace settings** and click the **Manage users** tab.
{% endstep %}

{% step %}
**Open the role dropdown on their row**

Find the person in the list and click the role dropdown on their row. It opens to show **Admin**, **Editor**, and **Viewer**, each with a one-line description, with their current role marked.

<figure><img src="/files/sfuYYvhW4cbcsIZ0I6wW" alt="A user row with the role dropdown open, listing Admin, Editor, and Viewer. Each role has a one-line description of what it can do, and the current role is marked."><figcaption><p>Role dropdown on a user's row, open</p></figcaption></figure>
{% endstep %}

{% step %}
**Select the new role**

Click the role you want. The change saves automatically, so the new role applies to that person right away, with no separate confirm step.
{% endstep %}
{% endstepper %}

To take someone's access away entirely instead of lowering it, see [How to remove a user](/account-and-team/users-and-roles/how-to-remove-a-user.md). Changing someone to **Viewer** keeps their access but limits them to viewing journey maps and commenting on cards. For what each role can do and how account access cascades to workspaces and maps, see [Access levels and permissions](/account-and-team/users-and-roles/access-levels-and-permissions.md).

#### Related topics

<table data-column-title-hidden data-view="cards"><thead><tr><th>Article</th><th>What it covers</th><th data-hidden data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Access levels and permissions</strong></td><td>What Admin, Editor, and Viewer can do, and how account access cascades to workspaces and maps.</td><td><a href="/pages/escpmNlj3DUgMgLSjGAl">/pages/escpmNlj3DUgMgLSjGAl</a></td></tr><tr><td><strong>How to invite users</strong></td><td>Add someone to the account, a workspace, or a single journey map and pick their role.</td><td><a href="/pages/F1Nzd1jlynqOnRaG0WSM">/pages/F1Nzd1jlynqOnRaG0WSM</a></td></tr><tr><td><strong>How to remove a user</strong></td><td>Revoke access at the account or workspace level and what the person loses.</td><td><a href="/pages/kAHKecCimBhsc1BbbgkZ">/pages/kAHKecCimBhsc1BbbgkZ</a></td></tr></tbody></table>


---

# 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://helpdesk.smaply.app/account-and-team/users-and-roles/how-to-change-a-users-role.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.
