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

# Team

> Manage your organization's team members and roles

Manage your organization's team members and their access levels in **[Settings → Team](https://usebugradar.com/settings?tab=team)**.

> [!NOTE]
>
> Only organization owners and admins can access team settings.

## Roles

| Role | Permissions |
| - | - |
| **Owner** | Full control: manage all settings, members, and integrations |
| **Admin** | Invite/remove members, manage integrations and agent settings |
| **Member** | Standard access to apps, flows, runs, and environments |

## Inviting Users

1. Go to Settings → Team
2. Click **Invite User**
3. Enter their name, email, and select a role
4. Click **Send Invitation**

The new user will receive an email invitation to join your organization.

You can also invite and remove members with the [Members API](/docs/api-members.md).

## When an invitee first signs in

The first time someone you invited signs in, whether from the invitation link or by signing up with that email, BugRadar shows **You've been invited** with your company's name. They click **Join** to join your company, which gives them access to every workspace in it. Someone invited by more than one company sees each one, picks where to start, and keeps access to all of them. They can switch anytime from the workspace menu.

After they join, the setup wizard opens on **Choose how to start** to help them run their first test. It skips the questions your company already answered, and they can close it anytime.

To start their own organization instead, they click **Create your own organization** under the button and name it. They stay a member of your company too.

## Teammates who sign up before you invite them

After someone signs up without an invitation, the setup wizard opens on **Name your organization**. Nothing is created until they click **Continue**. The step also shows **Joining your team?** with their email, marked **Waiting**, so they can ask an admin to invite them.

Someone who signs up by choosing a plan on the pricing page skips this step and goes straight to checkout, where the **Company name** they enter names the organization.

Invite that email from **Settings → Team**. Within a few seconds the wizard changes to **You've been invited**, and they join your company from there. No extra organization is made for them. If they close the page first, signing in again brings them back to the same step.

## Renaming a workspace

Workspace owners and admins can rename the active workspace in **Settings → Workspace → Details**. Edit **Workspace**, then click **Save workspace name**. The new name appears in the workspace picker; existing tests, runs, and memberships stay with the workspace.

## Deleting a workspace

Workspace owners and admins can delete the active workspace in **Settings → Workspace**. You can't delete your company's only workspace, and the workspace must be empty first: **Delete workspace** lists anything left (tests, suites, apps, scripts, schedules, connected integrations, a private network, or runs still in progress) with a link to where you remove each one. Tests and suites synced from a repo are removed by deleting them from the repo's `.BugRadar/` folder.

To confirm, type the workspace name. The workspace's run history is deleted with it and can't be recovered. Members are moved to another of your company's workspaces, and the workspace's API keys stop working.


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