> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/reference/roles-and-permissions.md).

# Roles and permissions

Two role systems: one at the organization layer, one at the workspace layer.

## Organization roles

| Action                         | Owner | Admin | Member |
| ------------------------------ | ----- | ----- | ------ |
| Edit organization name and URL | ✓     | ✓     | -      |
| View plan and usage            | ✓     | ✓     | -      |
| Invite members                 | ✓     | ✓     | -      |
| Revoke invites                 | ✓     | ✓     | -      |
| Change member roles            | ✓     | ✓     | -      |
| Remove members                 | ✓     | ✓     | -      |
| Leave the organization         | -     | ✓¹    | ✓      |
| Be removed by another admin    | -     | ✓     | ✓      |
| Access every workspace         | ✓     | ✓     | -      |
| Access only granted workspaces | -     | -     | ✓      |

¹ Admins can leave only if at least one other Admin remains. The owner can't leave or be removed. Transfer ownership through support.

## Workspace roles

Set per-member, per-workspace, when you invite a Member or change their workspace access.

| Action                                | Admin | Editor | Viewer |
| ------------------------------------- | ----- | ------ | ------ |
| Manage workspace settings and members | ✓     | -      | -      |
| Create products, workflows, audits    | ✓     | ✓      | -      |
| Edit products, workflows, audits      | ✓     | ✓      | -      |
| View everything in the workspace      | ✓     | ✓      | ✓      |

Organization Admins are implicitly **Admin** in every workspace and can't be downgraded at the workspace level. To restrict someone's workspace access, demote them to organization Member first.

## Special cases

* **Owner**: the user who created the organization. Always Admin at every layer. Can't be demoted, removed, or have their role changed within the app.
* **Last admin**: DevAlly blocks demoting or removing the last remaining Admin. Promote someone else first.
* **Self-demotion**: demoting yourself from Admin to Member loses you access to organization settings. DevAlly warns you and redirects to workspace settings on save.


---

# 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.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces/reference/roles-and-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.