Skip to main content
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. (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 console

Sign in to BotGauge to see your role and manage workspace access.

Try BotGauge →

​
Which settings each role sees

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

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