> For the complete documentation index, see [llms.txt](https://docs.corraldata.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corraldata.com/kb/getting-started/board-permissions.md).

# Board Permissions

Every Board now carries its own permissions, so the dashboards your team relies on can't be changed by accident. On top of your account role (Admin, Editor, Viewer — see [Add & manage users](https://docs.corraldata.com/kb/getting-started/manage-users)), each user can be granted a role on an individual Board.

### Board roles

| Board role | What it allows                                                                                  |
| ---------- | ----------------------------------------------------------------------------------------------- |
| Owner      | Full control: edit the Board and its widgets, and manage who has access and what role they hold |
| Editor     | Edit the Board and its widgets                                                                  |
| Viewer     | Open and use the Board — filters, date ranges, exports — without changing it                    |

A user's account role still sets their ceiling: someone who is a Viewer on the account can't be made an editor of a Board.

### Protecting a finished Board

Boards built for you by the CorralData team (or by your own data lead) can be locked down so end users get view access only, unless explicitly granted more. Widgets on a protected Board are covered by the same rules — no more surprise edits to a number the whole company watches.

If you open a Board you can't edit, you can still make your own version: choose **Duplicate to edit**, and work on the copy without touching the original.

### Managing access

Board owners manage access from the Board itself — add a teammate, pick their role, or change it later. You can also keep a Board entirely to yourself while you're building ("Only me"), then share it when it's ready.

{% hint style="info" %}
If you're having trouble and require technical assistance, feel free to reach out to <support@corraldata.com>.
{% endhint %}


---

# 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.corraldata.com/kb/getting-started/board-permissions.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.
