> For the complete documentation index, see [llms.txt](https://docs.kiln.fi/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiln.fi/v1/kiln-products/dashboard/members-and-roles.md).

# Members & roles

Choose what each member of your organization can do

Each member of your Kiln organization has a **role**. The role sets which actions they can take in the dashboard: staking, managing accounts, inviting people, or only viewing.

You manage members and roles in **Settings → Members**.

### Roles

|                                                     | Owner |       Standard       | Viewer |
| --------------------------------------------------- | :---: | :------------------: | :----: |
| View accounts, stakes, rewards and reports          |   ✅   |           ✅          |    ✅   |
| View organization settings and the audit log        |   ✅   |           ✅          |    ✅   |
| Stake, unstake, withdraw and other on-chain actions |   ✅   |           ✅          |    ❌   |
| Create, rename and delete accounts                  |   ✅   |           ✅          |    ❌   |
| Import, move and remove stakes                      |   ✅   |           ✅          |    ❌   |
| Invite members                                      |   ✅   | ✅ (as Standard only) |    ❌   |
| Remove members                                      |   ✅   |           ✅          |    ❌   |
| Manage API tokens                                   |   ✅   |           ✅          |    ❌   |
| Add and remove wallets                              |   ✅   |           ✅          |    ❌   |
| Approve or deny passkey reset requests              |   ✅   |           ✅          |    ❌   |
| Change a member's role                              |   ✅   |           ❌          |    ❌   |
| Invite a member as Owner or Viewer                  |   ✅   |           ❌          |    ❌   |
| Edit organization settings                          |   ✅   |           ❌          |    ❌   |

#### Owner

Full access to the organization. Only Owners can change members' roles, including granting the Owner role to someone else.

Every organization keeps at least one Owner: the last Owner cannot be demoted. To step down, promote another member to Owner first.

#### Standard

Can do everything on stakes and accounts, and invite new members, but cannot change roles or edit the organization's settings.

#### Viewer

Can see everything in the organization, but cannot change anything. Buttons for actions a Viewer cannot take are greyed out.

{% hint style="warning" %}
**All existing members are set to Owner by default.** Review your members in **Settings → Members** and switch them to Standard or Viewer where needed.
{% endhint %}

### Invite a member

1. Go to **Settings → Members**.
2. Click **Invite member**.
3. Enter the email addresses and pick the role the invitees will join with.
4. Click **Invite member**.

New members join as **Standard** unless you pick another role. Only Owners can invite someone as Owner or Viewer.

### Change a member's role

1. Go to **Settings → Members**.
2. Pick the new role in the **Role** column of the member's row.

The change applies to the member right away. It is recorded in the [audit log](https://docs.kiln.fi/v1/kiln-products/dashboard/audit-log.md).


---

# 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.kiln.fi/v1/kiln-products/dashboard/members-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.
