# Setting Rights

In this section, we will go through setting the proper rights for our To Do & TIVITY File classes.

For in-depth documentation about Rights, you can check out the following documentation page :

{% content-ref url="/pages/-M8Hj\_UaVWiMHpDIqtPC" %}
[Roles & Permissions (Team app)](/managing-users-and-collaboration/roles-and-permissions.md)
{% endcontent-ref %}

Each application has two predefined groups: **Editor** and **Viewer**. Like their name suggest, users in the **Editor** have both **Read & Write** rights, and users in the Viewer have only **Read** rights.

First to click on **Right** to access all groups for the application. 

![Accessing Rights](/files/-MA7Eax1XD4KSmYvyu4h)

### Setting up Editor Group

Click on **Editor** and head to the **Permissions Tab** and select **"Read + Write"** for both your To Do class and the TIVITY File class.

After setting the permissions, you must set yourself as a member of the **Editor** group. Head on to the Members Tab, click the plus icon :heavy\_plus\_sign:  and find your user. 

You will also notice going to the **Member Of Tab** that **Editor** is a member of the **Viewer** group.

![Editor Group Properties](/files/-MAXdPwv2TUX13rieLVL)

### Setting up Viewer Group

In the **Rights** window, click **Viewer**, head to the **Permissions Tab** and select **Read** for both your To Do class and the TIVITY File class.

As mentioned before you will notice that **Editor** is a member of the **Viewer** group in the **Members Tab**.

![Viewer Group Properties](/files/-MAXgrjYVddlSwPgDzzC)


---

# 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.tivity.one/overview/getting-started/setting-rights.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.