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

# Roles and sharing

A role determines workspace access. Sharing gives a teammate access to a specific workflow, queue or event type when supported.

| Role     | Use it for                                                                |
| -------- | ------------------------------------------------------------------------- |
| Admin    | Configure shared resources, integrations and workspace access.            |
| Member   | Use the resources made available to the member and manage personal setup. |
| Observer | Read permitted information without changing shared configuration.         |

## Share a resource

1. Open the workflow, queue or event type.
2. Use its sharing control.
3. Choose the workspace member.
4. Give **Can view** or **Can edit** access.
5. Save, then have the member check the resource from their own account.

Edit access includes viewing. It does not turn a member into a workspace admin or grant every integration permission. The resource's own restrictions and workspace feature access still apply.

## Decide who should edit

Give view access when someone needs to inspect configuration or investigate a run. Give edit access when they should change that specific resource. Keep shared routing-profile changes with people who understand all queues using the profile.

An Observer role is intended for reading. Personal notification preferences and other limited account actions can differ from shared configuration access.

If a resource does not appear, check the active workspace, role, sharing scope and feature activation. See [Feature availability](/get-started/availability.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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/settings/roles-and-sharing.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 `build a script that syncs our docs to a CMS` 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.