> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/rewards/users-and-roles.md).

# Users and Roles

Manage who can operate a Decentraland Rewards campaign by assigning roles and permissions to wallet addresses.

To perform any actions on a campaign within the Rewards service, you must be logged in with a wallet that has the necessary permissions.

When you create a campaign, you are automatically assigned as its owner and granted all permissions. As the owner, you can add other users to the campaign and assign them roles with specific permissions. However, each campaign can have only one owner—the creator—who is the only user with the authority to manage the funds.

To add a user to the campaign.

1. Click on the **User Roles** tab to view the list of users who have access to the campaign.
2. At the end of this list, you'll find a form to add a new user. Note: This form will only be visible if you have the necessary permissions to add users.
3. Complete the form by entering the user's wallet address (or ENS name) and selecting their role.
4. Click the **Add User** button to finalize the addition.

![
](https://45449780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoPnXBby9S6MrsW83Y9qZ%2Fuploads%2Fgit-blob-0881052dce8412b0737dbe3ac5e964953d288579%2Fusers.png?alt=media\&token=270df8af-ff97-42c2-8ad6-96f80eef1073)

## Permissions for roles

These are the actions allowed for each role:

| Permission                               | viewer | developer | collaborator | owner |
| ---------------------------------------- | :----: | :-------: | :----------: | :---: |
| View campaign name, network, and max gas |    ✅   |     ✅     |       ✅      |   ✅   |
| Edit campaign name, and max gas          |    ❌   |     ❌     |       ✅      |   ✅   |
| Activate and deactivate campaign         |    ❌   |     ❌     |       ✅      |   ✅   |
| View supply                              |    ✅   |     ✅     |       ✅      |   ✅   |
| Add/remove Supply                        |    ❌   |     ✅     |       ✅      |   ✅   |
| View dispensers                          |    ✅   |     ✅     |       ✅      |   ✅   |
| View dispenser key                       |    ❌   |     ✅     |       ✅      |   ✅   |
| Add/remove dispenser                     |    ❌   |     ✅     |       ✅      |   ✅   |
| View campaign transactions               |    ✅   |     ✅     |       ✅      |   ✅   |
| View users                               |    ✅   |     ✅     |       ✅      |   ✅   |
| Add/Remove users                         |    ❌   |     ❌     |       ✅      |   ✅   |
| Remove owner users                       |    ❌   |     ❌     |       ❌      |   ✅   |
| Manage funds                             |    ❌   |     ❌     |       ❌      |   ✅   |


---

# 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://docs.decentraland.org/creator/rewards/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.