> ## Documentation Index
> Fetch the complete documentation index at: https://www.botgauge.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Roles and permissions

> A complete matrix of BotGauge organization and workspace roles: who can invite people, manage projects and secrets, create API keys, and delete resources.

BotGauge has three organization roles and three workspace roles. The backend checks every action, so a hidden button is only for a cleaner interface. A call that isn't allowed returns an error (`403`, `404`, `409`, or `422`) and nothing changes.

## Organization roles

> **Owner**
>
> Everything an Org admin does, plus deleting the organization and making or removing owners.

> **Admin**
>
> Manages the organization, and the settings and members of every workspace, including new ones. Opens projects only in workspaces they belong to.

> **Member**
>
> Sees only the workspaces they're added to, with the role given there.

## Workspace roles

> **Admin**
>
> Manages members, projects, secrets, and API keys. Can rename or delete the workspace.

> **Member**
>
> Adds agents, runs attacks, and works on findings. Can create or rename projects and manage secrets.

> **Viewer**
>
> Sees agents, reports, and logs. Changes nothing.

In the API, these workspace roles are named `admin`, `editor` (shown as Member), and `viewer`.

## What each role can do

An org member gets the column of their role in each workspace. The same person can be Workspace admin of one workspace and Workspace viewer of another.

| Action | Org owner | Org admin | Workspace admin | Workspace member | Workspace viewer |
| - | - | - | - | - | - |
| Rename the organization, create workspaces, ask for more workspaces | Yes | Yes | No | No | No |
| Invite people, resend or cancel invitations, change org roles, choose a member's workspaces, remove people | Yes | Yes | No | No | No |
| Delete the organization, make or remove an owner | Yes | No | No | No | No |
| Rename or delete a workspace | Yes | Yes | Yes | No | No |
| Add or invite people to a workspace, change their workspace role, remove them | Yes | Yes | Yes | No | No |
| Create or rename a project, add, update, or delete a secret | Yes (1) | Yes (1) | Yes | Yes | No |
| Delete a project | Yes (1) | Yes (1) | Yes | No | No |
| See, create, or revoke API keys | Yes (1) | Yes (1) | Yes | No | No |
| See projects, agents, reports, and logs | Yes (1) | Yes (1) | Yes | Yes | Yes |
| Edit your own profile | Yes | Yes | Yes | Yes | Yes |

(1) Only in workspaces they belong to. In another workspace, an org owner or admin still manages settings and members, but its projects, agents, and logs return `404`.

Review roles in the consoleSign in to [BotGauge](https://cloud.botgauge.com) to see your role and manage workspace access.

[Try BotGauge →](https://cloud.botgauge.com)

## Which settings each role sees

| Settings area | Org owner or admin | Workspace admin | Workspace member | Workspace viewer |
| - | - | - | - | - |
| Account (profile) | Yes | Yes | Yes | Yes |
| Organization | Yes | No | No | No |
| Workspace, General and Members | Yes | Yes | No | No |
| Workspace, Projects | Yes (1) | Yes | Yes | No |
| Project, General and Secrets | Yes (1) | Yes | Yes | No |
| Project, API keys | Yes (1) | Yes | No | No |

A workspace member can create and rename projects and manage secrets, but can't delete projects or see API keys. A workspace admin's workspace pickers list only the workspaces they administer. A user with no workspace sees only their profile, plus a "No workspace yet" screen that tells them who to ask.

![The No workspace yet screen listing the admins to ask for access](https://mintcdn.com/botguage/CvMAYy1jOk7D5CuB/images/platform/no-workspace-yet.jpg?fit=max\&auto=format\&n=CvMAYy1jOk7D5CuB\&q=85\&s=6ffcc78ee5042da8404d2a8b958e0490)

People with no workspace see who to ask for access.

## Rules to remember

Nobody can give more access than they have. Only an org owner can make or remove an owner, and a workspace admin can never make someone an org admin.

An org admin manages every workspace. On a workspace's Members page they appear as "Org admin", with a fixed Admin role, no role dropdown, and no Remove option.

Removing someone from the organization takes them out of every workspace. Removing them from a workspace keeps them in the organization.

## Examples

| Person | Role | What they see in Settings |
| - | - | - |
| Vikram | Org owner | Everything |
| Ananya | Org admin | Everything except deleting the organization and changing owners. Projects only where she belongs. |
| Priya | Org member and Workspace admin of Payments | Profile, the Payments workspace, and its projects |
| Rahul | Org member and Workspace member | Profile, Payments projects, and Project General and Secrets |
| Meera | Org member and Workspace viewer | Profile only |
| Dev | Org member with no workspace | Profile only, plus the "No workspace yet" screen |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.