> ## 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.

# Organizations, workspaces, and projects

> How BotGauge organizes access: an organization contains workspaces, and each workspace contains projects with their own secrets and API keys.

BotGauge uses three levels. Each level has its own settings, and access flows down from the organization to the workspace to the project.

```mermaid theme={null}
flowchart TD
  O[Organization: your company] --> W1[Workspace: a team's space]
  O --> W2[Workspace]
  W1 --> P1[Project: agents, logs, secrets, API keys]
  W1 --> P2[Project]
```

| Level | What it is | Settings |
| - | - | - |
| **Organization** | The company. It has many workspaces. | General, Members, Workspaces |
| **Workspace** | A team's space. It has many projects. | General, Members, Projects |
| **Project** | Holds agents and logs, with its own secrets and API keys. | General, Secrets, API keys |

For example, an organization named Acme Inc. might have workspaces called Payments, Support, and Growth. The Payments workspace might hold projects named Refunds, Checkout, and Billing.

![The BotGauge sidebar switcher listing organizations, workspaces, and projects](https://mintcdn.com/botguage/CvMAYy1jOk7D5CuB/images/platform/switcher.jpg?fit=max\&auto=format\&n=CvMAYy1jOk7D5CuB\&q=85\&s=f6811358482a75117e6dc9b77e8212c4)

The switcher at the top of the sidebar moves you between organizations, workspaces, and projects.

## Roles at each level

Roles exist at the organization and workspace levels. Projects have no roles of their own. Everyone in a workspace opens every project in it, with their workspace role.

| Level | Roles |
| - | - |
| Organization | Owner, Admin, Member |
| Workspace | Admin, Member, Viewer |
| Project | None. Workspace roles apply. |

[Roles and permissions](https://www.botgauge.com/docs/platform/roles-and-permissions.md) lists what each role can do.

## Where traces go

Traces are sent with a project API key, so each project receives only the traces sent with its own keys. Secrets live at project level as well. If you run several agents or environments that should stay separate, create one project for each. Project creation is unlimited on every plan.

## Settings screens

Settings are grouped to match the three levels. Everyone sees **Account** and edits their own profile there. Organization settings are for owners and admins. Workspace and project settings appear according to your role in that workspace.

![The switcher open on the organization list](https://mintcdn.com/botguage/CvMAYy1jOk7D5CuB/images/platform/switcher-change-organization.jpg?fit=max\&auto=format\&n=CvMAYy1jOk7D5CuB\&q=85\&s=1c3938ad88383d12cc39fafdb5ac0772)

Use the switcher to change organization.

Set up your organizationOpen [BotGauge](https://cloud.botgauge.com) to create workspaces, projects, and invite your team.

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

> **[Roles and permissions](https://www.botgauge.com/docs/platform/roles-and-permissions.md)**
>
> Who can see and change what.

> **[Members and invitations](https://www.botgauge.com/docs/platform/members-and-invitations.md)**
>
> Add people, send invitations, and change access.

> **[Workspaces and projects](https://www.botgauge.com/docs/platform/workspaces-and-projects.md)**
>
> Create, rename, and delete.

> **[API keys](https://www.botgauge.com/docs/platform/api-keys.md)**
>
> Create the keys that send traces.


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