Teams and Workspaces
BB is built for teams, not just individuals. A shared workspace means everyone on your team works from the same context — the same projects, the same conversations with BB, the same progress.
How it all fits together
BB organises shared work in three layers:
Team
A team is a group of people in your organization. Each team has an owner, and can have team leads alongside its members. Everyone on the team gets access to the team's shared workspaces.
Workspaces
A team owns one or more workspaces. A workspace is a shared container for projects — think of it as a shared folder that everyone on the team can see and work inside. All projects you create inside a workspace are automatically visible to your whole team.
Projects and collaborations
Projects live inside workspaces. Each project contains your files and your collaborations with BB. Every collaboration inside a shared project is visible and editable by all team members — so if a teammate starts a conversation with BB, you can read it, continue it, or build on it.
What your team can see
Anything created inside a shared workspace — projects, collaborations, and the AI's work within them — is visible to everyone on the team. This is intentional. The goal is shared context, not siloed work.
In practice, this means:
- Any team member can open any project in the shared workspace
- Any team member can read any collaboration, continue it, or start a new one
- Work BB has already done — summaries, drafts, analysis — is available to whoever picks up next
- There's no 'catching up' — the context is already there
Workspace settings and who can change them
A shared workspace gives the whole team the same starting point. Its settings, in Settings > Workspace, are the defaults every project in the workspace begins with, so the team only sets things up once.
Who can change them: team leads and owners of the workspace's team, and organization owners and admins. Other members see the workspace settings read-only.
- Workspace Guidelines: instructions BB follows in every project of the workspace, such as house style or how your team works. Each project's own guidelines are added after them. Guidelines
- Personas: the workspace's personas set which model, guidelines and tool sets each role uses, unless a project chooses otherwise. Personas
- MCP servers: team leads and owners add and manage the workspace's MCP servers. Members can't change them, but where a server needs each person to sign in, members sign in for themselves. MCP Servers
- Agent Accounts: in shared team workspaces, agents can run as an agent service account instead of as the person who starts them. Agent Accounts
Organization owners and admins can see and manage the API tokens and MCP servers of every shared workspace in the organization.
Your personal workspace
Every BB user also has a personal workspace. Only you can see it — it's completely private from the rest of your team.
Use your personal workspace for work in progress you're not ready to share, personal notes and research, or anything that doesn't belong to a team project.
Shared memory and workspace context
BB's memory system is scope-aware. When you're working in a shared workspace, memories can be set at three levels:
Workspace-level memories are shared across the whole workspace — all team members can see and benefit from them. Use these for team conventions, shared client context, or anything the whole team should know.
Project-level memories are shared across all collaborations within a single project. Good for project-specific decisions, architecture choices, or domain knowledge relevant to that project.
Collaboration-level memories are specific to one collaboration. Use these for temporary notes or work in progress you're not ready to share more broadly.
Controlling which files BB can access
BB accesses files through data sources — connections to your files and services that you set up per project. You decide what each project can access.
Scoping file access to a project
For example: if you're working on a specific client, you can set up a Google Drive data source for that project with the root folder pointing to that client's folder. BB will only work with files in that folder — not the rest of your Drive.
This lets you work on multiple clients or projects without worrying about BB accessing the wrong files.
Note: BB reads file contents as part of completing tasks — your team members don't see a file browser. BB surfaces the information it needs from your files and works with it directly.
Getting your team set up
Organization owners and admins invite people and manage them in Settings > Organization > People: the Members tab lists everyone in the organization and has the Invite button, and the Teams tab is where they create teams, add members to them, and make a member a team lead. Invited people join the organization and get access to their team's shared workspaces.

Joining from an invitation
The invitation email links to a page showing the organization, who invited you, your role, the address it was sent to, and when the invitation expires. What you do next depends on whether you already have a Beyond Better account with that address:
- No account yet: choose Create account. The sign-up form has the invited address filled in. BB emails you to confirm it, and after confirming you come back to the invitation.
- You have an account: choose Sign in ("Already have an account with this address?") and you come back to the invitation.
- Signed in with the invited address: choose Accept and join. If you're signed in with a different address, the page offers to sign you out so you can continue with the invited one.
Don't want to join? Decline works without signing in. If the invitation has expired or was cancelled, the page says so; ask the person who invited you to send a new one. The same applies if the organization has no free seats.

Joining also gives you your own personal workspace. If BB opens it after you join, switch to your team's workspace with the workspace switcher to see the team's projects.
Next Steps
Managing Collaborations
Learn how to organise collaborations within a project and get the most out of shared context.
Data Sources
Connect BB to your files, services, and tools — and control exactly what each project can access.
Project Manager
How to create and manage projects, set project types, and organise your work.
Memory System
How BB remembers context across workspaces, projects, and collaborations — and how to control what gets shared.
Teams & Workspaces FAQ
Common questions about teams, workspace visibility, private projects, and file access.
Last updated: November 18, 2026