> For the complete documentation index, see [llms.txt](https://docs.terrastories.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrastories.app/using-terrastories/using-the-terrastories-member-dashboard/setting-up-users-and-roles.md).

# Setting up users and roles

{% hint style="info" %}
Managing users requires `admin` access. If you are logged in as an `editor`, `member`, or `viewer`, you will not be able to access this settings menu.
{% endhint %}

As an admin user, you can create, edit, and delete users that have access to your community in the **Users** view.

The Users view shows a list of all of the users that have access to your Terrastories community, and their respective level of access ("Role").

There are currently four **Roles** for a Terrastories community:

1. `admin` - has permission to view, add, or edit data (restricted and non-restricted); add or edit users; and change Theme settings.
2. `editor` - has permission to view, add, or edit data (restricted and non-restricted).
3. `member` - has permission to view data (restricted and non-restricted).
4. `viewer` - has permission to view data (non-restricted only).

<figure><img src="/files/3cwNSvU7iUXtFHFsmh5b" alt=""><figcaption></figcaption></figure>

There are several fields you can fill out for a User.&#x20;

* The ones that are required are **Username**, **Password** and **Role**.&#x20;
* The user's **Display Name** and **Photo** are currently only used in the content management system and a few areas on the main application, but we may start to use these more in the future.&#x20;
* It is also recommended setting an **Email** as we may make it possible in the future to permit users to recover their password if they've lost it.

<figure><img src="/files/iaGFik2n5qnNRQksjqAk" alt=""><figcaption></figcaption></figure>


---

# 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://docs.terrastories.app/using-terrastories/using-the-terrastories-member-dashboard/setting-up-users-and-roles.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.