---
title: "Team Projects"
description: "Team and invite-only project access, and working with team projects from the app, MCP, and CLI."
canonical_url: "https://docs.basicmemory.com/teams/team-projects"
---
# Team Projects

> Team and invite-only project access, and working with team projects from the app, MCP, and CLI.

Projects are how a team organizes its knowledge base. Every project in a team workspace has an access level, and every member's reach into it follows their [role](https://docs.basicmemory.com/teams/members-and-roles).

---

## Project access

<docs-video alt="Switching a project to invite-only, watching it disappear for a teammate, and opening it back up" poster="/videos/posters/docs-teams-access.png" src="https://docs.basicmemory.com/videos/docs-teams-access.mp4">



</docs-video>

Every project in a team workspace has an access level that decides who can find it:

<table>
<thead>
  <tr>
    <th>
      Access
    </th>
    
    <th>
      Who can see it
    </th>
    
    <th>
      When to use
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Team
      </strong>
      
       — <em>
        default
      </em>
    </td>
    
    <td>
      Everyone in the team, according to their <a href="https://docs.basicmemory.com/teams/members-and-roles">
        role
      </a>
    </td>
    
    <td>
      Most team work — the open, shared knowledge base
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Invite-only
      </strong>
    </td>
    
    <td>
      Only the teammates you invite to it
    </td>
    
    <td>
      Sensitive topics — hiring, contracts, security reviews — or work you want to keep to yourself. Creating one needs the Business plan
    </td>
  </tr>
</tbody>
</table>

### Changing a project's access

Open **Settings → Projects**. Each project lists its current access underneath its name. Click **Edit Access**, choose **Team** or **Invite-only**, and save.

Access can be changed at any time — it isn't fixed when the project is created.

### Choosing who can see an invite-only project

An invite-only project gets a **Manage Members** button next to **Edit Access**. Use it to invite specific teammates. Anyone you don't invite can't find or open the project.

An invite-only project with nobody invited is visible only to you. That's the way to keep drafts or scratch work in a team workspace without the rest of the team seeing them.

<note>

**Keeping something entirely out of the team is simpler than it looks.** Your [personal workspace](https://docs.basicmemory.com/teams/about#workspaces) is separate from every team you belong to, and teammates never see it. You only need an invite-only project when the work should live in the team workspace but stay narrow.

</note>

<note>

**Setting access from the CLI.** As of v0.24, `bm project add --cloud --visibility workspace|shared` sets the project's access (`workspace` is **Team**, `shared` is **Invite-only**), and `--visibility private` is refused. Earlier CLIs accepted all three values and ignored them, creating every project Team-visible ([basic-memory#1343](https://github.com/basicmachines-co/basic-memory/issues/1343)). The CLI can't read a project's access level back, so confirm it in the app.

</note>

See the [CLI Reference](https://docs.basicmemory.com/reference/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 list` shows projects across all your workspaces. As of v0.24, a team project with a local sync path is listed as syncable rather than `cloud-only`.

### Syncing team projects with local files

`bm cloud pull` and `bm cloud push` are the sync workflow for team projects. They are additive (never delete on the destination), authorized per project — read access to `pull`, edit access to `push` — and need no `bm cloud setup`. In v0.24 they list the project in one request and transfer eight files at a time, so large team projects sync much faster.

```bash
bm cloud sync-setup team-wiki ~/team-wiki
bm cloud pull --name team-wiki
bm cloud push --name team-wiki
```

The deprecated `bm cloud sync` and `bm cloud bisync` mirror commands exit on team workspaces with a notice pointing at `pull`/`push`. See [Cloud Sync](https://docs.basicmemory.com/cloud/cloud-sync).

### Removing a team project

`bm project remove <name> --cloud` permanently deletes the project's cloud files for everyone in the team — there is no keep-files option. The CLI asks for confirmation and reminds you that deleted files can be recovered only from a snapshot (`bm cloud snapshot list`). See [Remove a Cloud Project](https://docs.basicmemory.com/cloud/cloud-guide#remove-a-cloud-project-and-its-data).

### Workspace commands

```bash
# 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 (`bm_project(command="create", 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**:

```text
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](https://docs.basicmemory.com/teams/copy-between-workspaces) for the project ZIP, single-note, MCP, and local-sync workflows, along with caveats around wikilinks, permissions, and share links.

---

## Next Steps

<card-group>
<card icon="i-lucide-copy" title="Copy Content Between Workspaces" to="https://docs.basicmemory.com/teams/copy-between-workspaces">

Move personal notes into the team workspace.

</card>

<card icon="i-lucide-route" title="Local & Cloud Routing" to="https://docs.basicmemory.com/cloud/routing">

Run some projects locally and others in the cloud.

</card>

<card icon="i-lucide-terminal" title="CLI Reference" to="https://docs.basicmemory.com/reference/cli-reference">

Full `bm project` and `bm cloud workspace` commands.

</card>
</card-group>


## Sitemap

See the full [sitemap](https://docs.basicmemory.com/sitemap.md) for all pages.
