Workspaces
Version: 3.0 | Last updated: 2026-11-11
A workspace is your shared environment in Bluebox. One is created for you automatically when you sign up. You can create additional workspaces, invite teammates, and switch between them from the workspace menu. Everything in Bluebox (findings, investigations, connections) belongs to a workspace.
Because each workspace has its own web address, you can open different workspaces in separate browser tabs and work in them side by side. Each tab stays on its own workspace, so switching workspaces in one tab never changes what the others are showing.
Workspace owners manage membership and can invite or remove members. If you're added to a workspace, a notification in the bell tray ("You've been added to the workspace …") links to it until you open it for the first time. You can dismiss the notification without opening the workspace.
Owners and members
A workspace has two roles. Members work in the workspace: they create investigations and chats, and they see their own work plus whatever has been shared with them. Owners do all of that and manage the workspace itself: inviting and removing people, changing roles, managing connections and tokens, and deleting the workspace. An owner can also open and edit any investigation or chat in the workspace, including private ones, write access by the owner to content they do not personally own is audited.
Because ownership is that broad, Bluebox asks you to confirm before granting it. Note that a new owner has the same powers you do, which includes changing your role or removing you.
Owners change roles from Settings → Users & sharing. You can't change your own role or remove yourself (use Leave workspace instead), and a workspace always keeps at least one owner, so the last one can't be removed or demoted until someone else is made an owner.
The member list in workspace settings (Settings → Users & Sharing) shows each member's name, email address, role, and status, and is searchable by any of them.
A member's role is shown as a chip in the Role column, and for workspace owners that chip is also the control that changes it. Open it and pick Member or Owner; the role currently in effect is checked. Bluebox asks you to confirm before the change takes effect and spells out what it grants or removes, because an owner can open and edit every investigation and chat in the workspace, including private ones, and can manage members, connections, and the workspace itself.
You can't change your own role from owner to member, so a workspace is never left without someone able to manage it. Another owner can do it for you.
Only workspace owners can change roles or remove members. Everyone else sees the same list, read-only.
What workspace owners see
A workspace owner sees everything in the workspace, including every member's private chats, investigations, and routines. Bluebox labels each item by why you can see it:
- Only me: your own item, not shared. You and workspace owners see it.
- Workspace: your item, shared read-only with every member.
- Shared with you: another member shared it with the workspace. You can read it.
- Owner access: another member's item that is not shared. You see it only because you are a workspace owner. Other members cannot.
Invite teammates to your workspace
Workspace owners invite teammates by email from workspace settings. Where email delivery is switched on, Bluebox emails the teammate a join link and tells you so, naming the address it sent to. You also always get the join link to copy, so you can share it over chat if the email is slow or lands in spam. Where email delivery is switched off, Bluebox says no email was sent and the copy-and-share link is the only route. The teammate does not need a GitHub account. They can open the link and sign in with email, which sends a link and six-digit code to the address they enter, or with GitHub. Either way the teammate signs in, opens the link, reviews the invitation, and chooses to accept (joining your workspace) or decline.
When you pick the Owner role, the invite form warns you that an owner can do everything in the workspace, including opening every member's private chats and investigations. The invitation the teammate opens says the same before they accept.
Invitations expire so old links don't stay valid forever. You choose how long each invitation stays valid when you create it: from 1 to 14 days, defaulting to 7 days. Expired invitations are cleaned up automatically, and the expiry you pick applies only to that invitation.
If a teammate declines, the invitation stays in your list marked Declined, with the date they declined it, so you can tell a decline apart from an invitation nobody has opened yet. Bluebox doesn't notify you when this happens: the list updates on its own while workspace settings is open, in the same way it does when someone accepts. A declined invitation no longer takes up a seat, and you can invite the same person again at any time. Declines drop off the list after 30 days, or you can clear them yourself with Dismiss on a single row or Dismiss all declined.
Each workspace has a member limit. Once the workspace reaches that limit (counting current members plus invitations that are still pending), creating another invitation is blocked until a seat frees up. Remove a member or revoke a pending invitation to make room, then invite again. The invite form shows current members against the limit so you know where you stand before inviting.
Workspace settings keep themselves up to date while the page is open: when a teammate accepts an invitation or someone requests access, the member list, pending invitations, and access requests refresh on their own; you don't need to reload the page.
A teammate who joins by invitation joins your workspace; they don't get a separate one. They can still create their own workspace later from workspace settings if they need one.
When someone asks to join
If you're a workspace owner, the notification tray in the header tells you when someone has asked for access, so nobody has to keep a settings page open to find out. The request comes with Approve and Decline right there, plus a link to Settings → Users & sharing—which lists everything still waiting and shows the message the person sent with their request.
Only owners see these. Nobody else in the workspace can act on a request, so putting it in front of them would cost them attention for a decision they can't take—and hand them the requester's email address along the way.
That's the only membership notification. Everything else—someone joining, an invitation declined or expired, a member removed, a role changed—is a fact you can read off Settings → Users & sharing whenever you need it, and nobody has to answer it, so the tray stays quiet.
If you don't see the tray, notifications aren't switched on for your workspace yet.
The number on the bell counts notifications you haven't seen yet, not everything still in the tray, plus any "You've been added to the workspace" notice, which stays counted until you open that workspace or dismiss it. Opening the tray marks what it shows as seen, so the number clears; the notifications stay in the tray until you dismiss them. Anything that arrives while the tray is open still counts the next time you look. Each workspace keeps its own count, so reading notifications in one workspace doesn't clear the bell in another.
When someone opens a shared link to a workspace they're not in yet, they can request to join it. Workspace owners see these requests in the Access requests list in workspace settings (Settings → Users & Sharing).
While any request is pending, a dot shows on your profile avatar in the sidebar. It disappears once there are no pending requests left.
When a request arrives while you have Bluebox open, a notification appears with a Review request link that opens the Access requests list directly, so you can act on it without hunting for the page.
Each request shows who is asking: name, email, or GitHub login. Approve adds them to the workspace as a member; Decline leaves them without access. If the workspace is at its member limit, free a seat before approving. The list is searchable and paged, so it stays manageable as requests come in.
To help someone send a request in the first place, the Access requests panel shows your workspace link with a Copy link button. Copy it and share it with the person who needs access, or share a link to any investigation you've shared. When they open it while signed in but not yet a member, they can request to join, and the request appears in this list.
When someone is removed
Removing a member takes effect immediately: they're signed out of that workspace and any routines they scheduled there stop running. Their investigations and chats stay in the workspace, and anything they shared stays visible to the people they shared it with. You can invite them back later, and they get their work back, but their scheduled routines stay off until someone turns them back on, and they count against the workspace member limit again.
Share a link to your workspace
Every page in Bluebox carries your workspace in its address, so you can copy the link from your browser bar, or use the Copy link button on investigation, task, and overview pages, and send it to anyone.
Workspace links share a consistent shape: /w/{workspaceRef}, where {workspaceRef} identifies your workspace. Every workspace page (Overview, investigations, tasks, and chat) lives under that /w/{workspaceRef} prefix, so any link you copy already points at the right workspace. This is the canonical shape for a shared workspace link; older links you saved before this format are still understood and open the same place.
Sharing a link is not the same as adding someone: opening it never grants access on its own. A teammate who is already a member lands on the exact page in the right workspace. Someone who isn't a member yet sees a Request access option instead of a dead end, and the request comes to the workspace owners to approve.
Request access to a workspace
If you open a link to a workspace you're not a member of, Bluebox offers to request access rather than showing an error. A workspace owner then approves or declines your request, and once approved the workspace opens for you.
If you can't access the workspace a link points to, you land on a dedicated page instead of the app. From there you can request access and wait for a workspace owner to approve. If you already belong to a workspace of your own, you can open it from the same page instead of waiting; a pending request never keeps you out of your own workspace. You can also create your own workspace; nothing is created for you until you choose to. If you've reached your plan's free-workspace limit, the page explains that instead of offering to create another.
If a workspace owner declines your request, the page tells you so and lets you ask again. You can sign out from this page at any point.
Create additional workspaces
You can create separate workspaces, each with its own connections and repositories, from workspace settings. Your plan sets a limit on how many free workspaces you can create and own. Joined workspaces do not use that allowance. Pro workspaces do not count against the free-workspace allowance, so upgrading a workspace to Pro frees up your free-workspace slot to create another one.
The Add workspace section shows how many workspaces count against your limit. Once you reach it, the section is blocked with an explanation instead of letting you name a workspace and fail on create. Delete a workspace you own to free up a slot, then create again.
Your default workspace
If you work in more than one workspace, you can pick one to open by default. In workspace settings, open the workspace you want and turn on Open this workspace by default. Bluebox remembers the choice across sign-ins, so opening Bluebox without a specific link takes you straight there. To go back to no fixed default, turn it back off.
When you open Bluebox, it decides where to land in this order:
- A workspace link in the address bar wins: that tab opens exactly the workspace the link names.
- Otherwise, your default workspace, if you set one.
- Otherwise, the workspace you used most recently.
- Otherwise, if you belong to only one workspace, that one.
- Otherwise, Bluebox shows a chooser so you can pick.
If your default or most-recent workspace is no longer available (you left it, or it was removed), Bluebox ignores the stale choice and shows the chooser instead of sending you somewhere you can't open.
Investigation-finished email
Where available, workspace settings offer Email me when an investigation finishes, covering both investigations that start automatically and ones a schedule runs on your behalf. It's on by default — Bluebox emails you when one of those finishes, with a link straight to the result. Turn it off if you'd rather check in from the app instead.
Approval-request email
Selective preview
Workspace settings also offer Email me when my approval is needed, for the emails Bluebox sends when a tool call needs your approval. It's on by default. Turn it off if you'd rather check in from the app instead; you still see the approval in Bluebox either way.
After you delete or leave a workspace, Bluebox always shows the chooser, even if you have only one workspace left.
Turn on log monitoring
Selective preview
Workspace owners can enable Log monitoring in workspace settings. When on, Bluebox opens AI investigations for new error-log pattern findings it detects in your workspace.
- Log monitoring is off by default for every workspace. Only the workspace owner can enable it.
- Error log clustering runs continuously in the background for all workspaces with a connected observability backend. Enabling log monitoring does not start new queries against your logs — it controls whether Bluebox opens investigations for the patterns it finds.
- It is independent of auto-investigations: investigations are created only when both log monitoring and auto-investigations are enabled.
- When you enable log monitoring, Bluebox opens investigations only for error patterns with new occurrences after you enabled it. Existing patterns that have not recurred since you enabled the setting are not surfaced — enabling does not open a historical backlog.
- If you disable and re-enable log monitoring, the same rule applies: only patterns with new occurrences after the most recent re-enable are candidates for investigation.
Log monitoring requires a connected observability backend with log access.
Give the agent workspace instructions
When it is available for your workspace, workspace settings offer a place for owners to add free-form instructions that apply to every chat and investigation in the workspace, for example explaining how your environments are set up, or a convention specific to your team. Bluebox follows this guidance alongside its own safety rules, and every member sees the same instructions applied. Leave it blank and nothing changes. If you do not see this section, it is not enabled for your workspace.
Workspaces you haven't opened yet
When you're added to a new workspace, a notification appears in the bell tray at the top right ("You've been added to the workspace …") and counts toward the bell's badge. Select the workspace name or the row to open it. The workspace menu also shows a small blue dot next to that workspace. Open the workspace once and both clear for good. You can also dismiss the notification with its x, which hides it in this browser without opening the workspace. If you belong to more than one new workspace, each gets its own notification until you visit it.
How shared workspaces work
The first time you open a workspace you don't own, Bluebox shows a one-time welcome that names the workspace and its owner and explains how sharing works there:
- Everything you create (investigations, chats) starts private: visible only to you and workspace owners. Nothing you create becomes visible to other members until you choose to share it.
- Sharing an investigation is an explicit action, and it grants read-only access. A member you share with can view and comment, but can't change it.
- Only an investigation's owner or the workspace owner can edit, archive, or otherwise change it.
- The workspace owner can open any investigation or task in the workspace, including private ones. Your own task list still shows only your work.
- A chat is private to whoever started it until they share it, and sharing a chat grants read-only access just like an investigation.
You can reopen this explanation anytime from the workspace menu: select How this shared workspace works.
Opening a link to someone else's private item
If a teammate sends you a direct link to an investigation, chat, or routine run that they haven't shared with the workspace yet, Bluebox shows you a notice rather than a generic "not found" page. The notice names the creator (when they're still a workspace member) and tells you what to ask them to do:
- For an investigation or routine run: ask the creator to set its sharing to Workspace.
- For a chat: ask the creator to share it with the workspace.
You can't request access to the item itself — that action is up to the creator. Once they share it, the link will open normally.
If the link really is broken or no longer exists, you'll see a different message that explains the link is invalid and asks you to request a fresh one.