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

# Roles

Organization and workspace roles and their permissions

{% hint style="info" %}
**Takeaways**

* Organization roles govern account-wide access, Context, Findings, SCM connections, and workspace creation.
* Workspace roles govern private plugins, publishing, evals, workspace members, and CLI scan uploads.
* A user can hold different roles in different workspaces.
  {% endhint %}

## Organization roles

Organization roles are assigned across the Organization. An Organization admin also inherits the owner role in every workspace in that Organization.

| Permission                                                          | member | admin |
| ------------------------------------------------------------------- | ------ | ----- |
| View Organization-owned Context, Findings, and scan history         | Yes    | Yes   |
| View SCM connections and scan history                               | Yes    | Yes   |
| Ignore or restore Findings                                          |        | Yes   |
| Manage Organization-scoped API keys                                 |        | Yes   |
| Create workspaces                                                   |        | Yes   |
| Connect or remove SCM accounts, set scan scope, and trigger rescans |        | Yes   |
| Inherit owner access in every workspace                             |        | Yes   |

Context and Findings from a workspace-owned upload remain visible only to people who can view that workspace.

## Workspace roles

Workspace roles are assigned per workspace. To learn more about creating a workspace, see [Workspace management](/reference/cli-commands.md#workspace-management).

| Permission                                         | consumer | member | publisher | manager | owner |
| -------------------------------------------------- | -------- | ------ | --------- | ------- | ----- |
| View and install private plugins in the workspace  | Yes      | Yes    | Yes       | Yes     | Yes   |
| View workspace users and permissions               |          | Yes    | Yes       | Yes     | Yes   |
| Generate workspace-scoped API keys                 |          | Yes    | Yes       | Yes     | Yes   |
| Review, security-scan, and fix skills from the CLI |          | Yes    | Yes       | Yes     | Yes   |
| Generate eval scenarios                            |          |        | Yes       | Yes     | Yes   |
| Run evals                                          |          |        | Yes       | Yes     | Yes   |
| Manage eval visibility                             |          |        | Yes       | Yes     | Yes   |
| Create and publish plugins                         |          |        | Yes       | Yes     | Yes   |
| Unpublish a plugin within two days of publishing   |          |        | Yes       | Yes     | Yes   |
| Roll out plugins to repositories                   |          |        | Yes       | Yes     | Yes   |
| Upload a scan with `tessl inventory import`        |          |        | Yes       | Yes     | Yes   |
| Set up and manage workspace integrations           |          |        |           | Yes     | Yes   |
| Invite users and change workspace permissions      |          |        |           | Yes     | Yes   |
| Remove other managers                              |          |        |           | Yes     | Yes   |
| Archive plugins                                    |          |        |           | Yes     | Yes   |
| Edit or delete workspace-scoped API keys           |          |        |           | Yes     | Yes   |
| Add or remove workspace owners                     |          |        |           |         | Yes   |
| Delete the workspace                               |          |        |           |         | Yes   |


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tessl.io/administrators/roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.