# User Management

There are three user tiers within Tourial: Viewer, Editor, and Admin.

### Admin Permissions <a href="#h_e31bef89f9" id="h_e31bef89f9"></a>

As an Admin, you'll see an option for Manage Users under Settings.<br>

<figure><img src="/files/4ci5qj3l28ueO0zUkPDj" alt=""><figcaption></figcaption></figure>

Admins have additional permissions on top of being an Editor and can do the following:

* Add a subdomain (for Engagement Data)
* Create new users
* Edit an existing user
  * Change their user role (Viewer, Editor, or Admin)
  * Update email addresses (in case of initial typos, etc.)
* Deactivate a user
* Re-activate a deactivated user
* View a list of all active & inactive users (Admins cannot delete users)
  * The active and inactive user list displays:
    * Name
    * User email
    * Role *(Access Level)*
    * Active/Inactive toggle
    * Created date
    * Last Activity date

### Editor Permissions <a href="#h_800cd2b900" id="h_800cd2b900"></a>

As an Editor, you have full access to Tourial functionality to build Tours, connect Integrations, add Branding, etc.\
​\
Editors are not able to create, manage or view Account users (as listed above for Admins).

### Collaborator Permissions <a href="#h_800cd2b900" id="h_800cd2b900"></a>

As a Collaborator you have the ability to create tours and make edits to any **non-live** (Draft or Unpublished) tours. Collaborators do not have the ability to publish tours.&#x20;

### Viewer Permissions <a href="#h_1cdc3e091a" id="h_1cdc3e091a"></a>

As a Viewer, you can see everything in Tourial (Tours, Forms, etc.) and grab Share links. Viewers are not able to create Tours or edit existing Tours.


---

# Agent Instructions: 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:

```
GET https://docs.navless.ai/admin-and-settings/user-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.