Team Projects
Projects are how a team organizes its knowledge base. Every project in a team workspace has a visibility, and every member's access follows their role.
Project visibility
Team projects come in three visibilities. The right one depends on who needs to see the work:
| Visibility | Who can see it | When to use |
|---|---|---|
Standard (workspace) — default | Everyone in the team, based on their team role | Most team work — the open, shared knowledge base |
Shared (shared) | Only people you grant access to, each with view or edit access | Sensitive topics (hiring, contracts, security audits) where you want a controlled group |
Private (private) | Just you | Drafts and scratch work that isn't ready for the team |
When you create a cloud project, you can set its visibility from the CLI:
# Standard — visible to everyone in the team workspace (default)
bm project add team-wiki --cloud --workspace acme --visibility workspace
# Shared — only people you grant access to
bm project add hiring-2026 --cloud --workspace acme --visibility shared
# Private — just you
bm project add my-scratch --cloud --workspace acme --visibility private
See the CLI Reference for full bm project add options.
Working with team projects
Once you're part of a team, projects show up everywhere you work:
- In the app — Select the project in the sidebar.
- In your AI assistant (MCP) — your assistant's project list spans every cloud workspace you can access, so it reaches team projects without extra setup.
- In the CLI —
bm project listshows projects across all your workspaces.
Workspace commands
# List the cloud workspaces available to you
bm cloud workspace list
# Set the default workspace for CLI and MCP routing
bm cloud workspace set-default acme
You can also target a specific workspace when creating a project, either from the CLI (--workspace) or from MCP (create_memory_project(workspace="acme")).
Targeting a team project explicitly
If a project name exists in more than one workspace (say, research in both your personal and team workspaces), resolution prefers your default workspace — or asks you to disambiguate. To be explicit, use a workspace-qualified memory URL:
memory://acme/research/architecture-decisions
The form is memory://<workspace-slug>/<project>/<path>. From the CLI, pass --workspace on the command instead.
Bringing existing notes into a team project
When you join (or start) a team, you'll often want to promote work from your personal workspace into the shared one. Cross-workspace transfers are a copy workflow — export from the source, import into the target, verify, then optionally delete the original.
See Copy Content Between Workspaces for the project ZIP, single-note, MCP, and local-sync workflows, along with caveats around wikilinks, permissions, and share links.