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

# Users and roles

Invite, change, and remove users; role and access reference

Managing who has access to your account and workspaces, and what they can do.

#### Why use users and roles

* Control who can reach your account, workspaces, and individual journey maps
* Grant the right level of access (Admin, Editor, Viewer) at each scope without over-sharing

#### In this section

* [**Create account**](https://helpdesk.smaply.app/account-and-team/users-and-roles/how-to-create-an-account.md) - Sign up from the marketing site or use the in-app Add account flow.
* [**Join by invitation**](https://helpdesk.smaply.app/account-and-team/users-and-roles/how-to-join-by-invitation.md) - Accept an invitation, whether you're new to Smaply or an existing user.
* [**Switch accounts**](https://helpdesk.smaply.app/account-and-team/users-and-roles/how-to-switch-between-accounts.md) - Change the active Smaply Account when you belong to multiple.
* [**Access levels and permissions**](https://helpdesk.smaply.app/account-and-team/users-and-roles/access-levels-and-permissions.md) - Reference for Smaply's role and scope model: Admin, Editor, Viewer at Account, Workspace, Journey Map.
* [**Invite users**](https://helpdesk.smaply.app/account-and-team/users-and-roles/how-to-invite-users.md) - Invite users at account, workspace, or journey-map level. Covers all roles (Admin, Editor, Viewer).
* [**Change a user's role**](https://helpdesk.smaply.app/account-and-team/users-and-roles/how-to-change-a-users-role.md) - Change roles at account or workspace level.
* [**Remove a user**](https://helpdesk.smaply.app/account-and-team/users-and-roles/how-to-remove-a-user.md) - Remove users and understand what they lose access to.


---

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