> For the complete documentation index, see [llms.txt](https://docs.graphite-note.com/graphite-note-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graphite-note.com/graphite-note-documentation/~/changes/E2AMshWWxt1bMPRlFt2a/account-and-team-setup/roles.md).

# Roles

Each user in a team can have a role that you can see on the “users page” (more information on [Team setup](/graphite-note-documentation/~/changes/E2AMshWWxt1bMPRlFt2a/account-and-team-setup/team-setup.md)). There are two types of roles :

* Administrator: can read and modify entities
* Viewer: can only read entities, no editing allowed

The details are accessible through the *Account* tab in the top-right corner of Graphite Note, followed by selecting the *Roles* option from the drop-down menu.

If you want to change the properties of the viewer mode, you can click on the gear wheel to edit it.

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

You can now not allow access to some modules or give the possibility of editing them. You have also the possibility of deleting the role.


---

# 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.graphite-note.com/graphite-note-documentation/~/changes/E2AMshWWxt1bMPRlFt2a/account-and-team-setup/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.
