Manage your workspaces

This guide shows you how to create workspaces, invite team members, and switch between projects.

What workspaces are for

Workspaces isolate your data. Each workspace has its own:

• Conversations and traces - monitor hallucinations separately per project
• Experiments - compare models without mixing results
• Hallucination configs - tailor detection to different use cases
• Team members - control who can access each project

Use separate workspaces when you need:

• Different environments (development, staging, production)
• Separate projects or clients
• Teams that shouldn't see each other's data

Create a workspace

1. Click Workspaces in the sidebar.
2. Click Create Workspace.
3. Enter a name for your workspace.
4. Edit the URL slug if needed. Blue Guardrails generates one from your name.
5. Click Create.

Your new workspace appears in the table.

Switch between workspaces

Use the workspace selector at the top of the sidebar.

1. Click the dropdown showing your current workspace name.
2. Select the workspace you want to switch to.

Blue Guardrails loads the new workspace's dashboard.

Invite team members

You can invite users to workspaces you own.

1. Click Workspaces in the sidebar.
2. Find your workspace in the table. Look for the "Owner" badge.
3. Click Invite.
4. Enter the email address of the user you want to invite.
5. Click Send Invite.

The user must have a Blue Guardrails account with that email address.

Invited members can view and create all workspace data: conversations, experiments, and hallucination configs. Only you as the owner can change workspace settings or remove members.

Usage from all members is charged to your billing account as the workspace owner.

Copy your workspace ID

If you need your workspace ID for API requests:

1. Look for the copy button next to the workspace selector in the sidebar.
2. Click it to copy the workspace ID to your clipboard.

Use workspaces with the API

When you send traces to Blue Guardrails, you need to specify which workspace receives them.

Option 1: Workspace-scoped API key

Create an API key that's tied to a specific workspace. All traces sent with this key go to that workspace automatically.

Option 2: x-workspace-id header

Use a user-level API key and include the x-workspace-id header with each request. Set the header value to your workspace ID.

x-workspace-id: your-workspace-id

If you use a workspace-scoped key and also send the header, the header must match the key's workspace.