Basic Memory
Teams

Joining a Team Workspace

First-time setup for new team members — accept the invite, sign in, switch workspaces, and connect your AI assistant to the shared knowledge base.

You got an invite to a Basic Memory team workspace. This page walks through what to do on day one — accept the invite, get into the workspace, find the shared projects, and point your AI assistant at the same knowledge base.

You'll need a Basic Memory account on the email address the invite was sent to. If you don't have one yet, the accept flow walks you through creating it.

1. Accept the invitation

Open the invitation email and click the Accept invitation link. It opens an accept page in the app.

  • Click Accept — the app then routes you through sign-in.
  • Sign in with the email the invite was sent to (you'll create an account during sign-in if you don't have one).
  • If you're already signed in with a different account, the app will prompt you to sign in again with the invited email.

On first sign-in, your account is linked to the pending membership, and you become an active team member.

2. Find the projects

Your team appears as its own section in the sidebar, alongside your personal workspace, with its projects listed underneath. Open one to see its folders and notes.

Your role determines what you can do — from read-only Viewer up to Owner, with Editor, User Admin, and Admin tiers in between. The full capability table is on Members and Roles.

Not sure of your role? Open Settings → Teams to see your teams and your role in each. If you need a different role, ask an owner, admin, or user admin — they manage members from Settings → Members.

3. Connect your AI assistant

Your assistant works with the team workspace through the same MCP endpoint as your personal cloud. Pick the path that matches your tool:

  • Claude Desktop / Claude Code — see Claude Desktop or Claude Code. Use the OAuth flow; your assistant will see team projects automatically once you've accepted the invite.
  • ChatGPT — see ChatGPT.
  • Codex / Cursor / VS Code / Obsidian — see the integrations index.
  • CLI — bm cloud login once, then bm project list shows projects across every workspace you can access (personal and team).
With v0.21, your assistant's project list spans every workspace you can reach, so team projects show up without extra configuration. See v0.21.0 for the cross-workspace discovery story.

Targeting the team workspace explicitly

If you want a CLI command or MCP call to act on a team project (and avoid ambiguity with a same-named personal project), be explicit:

# Make the team workspace your default
bm cloud workspace set-default acme

# Or target it per command
bm project list --workspace acme

From MCP, pass the workspace through create_memory_project(workspace="acme"), or reference notes with a workspace-qualified memory URL — memory://acme/research/note-title. See Team Projects for the full targeting guide.

4. Get oriented

A few good first steps in any new team workspace:

  • Browse the project tree to see what your team already has.
  • Search a topic you care about — see what's already been written.
  • Pin the notes you'll come back to.
  • Read the team's conventions if they've documented any (look for an onboarding, README, or team-norms note).

Bringing your existing notes with you

Already have personal notes you want to share with the team? Cross-workspace transfer is a copy workflow — see Copy Content Between Workspaces for the project ZIP, single-note, and MCP recipes.

Related

Team Projects

Project visibility, sharing, and working with team projects from the app, MCP, and CLI.

Copy Content Between Workspaces

Move notes, folders, or whole projects between personal, team, and local workspaces using export/import or MCP.