# Share Projects and add devices Start in **Projects**. A Project is the canonical repository whose memories you want to share; linked worktrees belong to that Project, while unrelated repositories with the same short name remain separate. Select the Projects, choose **Add Teams or Identities**, and review the recipients and resulting access before confirming. A Team groups Identities. An Identity is a recipient security context, and one person can have separate personal and work Identities. Sharing with a Team includes its eligible current and future members. Sharing with an Identity adds direct access independently of Team membership. Joining a Team does not automatically share every Project on your machine. **Add Teams or Identities** only adds sharing. Each choice shows its saved direct coverage across the selected Project entries separately from its checkbox. An unchecked box means no addition requested. Partially covered choices start unchecked, and fully covered choices cannot request another addition. Access through a Team appears separately from direct Identity access. **Update sharing** on one Project shows saved direct relationships as checked boxes. Removing one relationship can leave access through another Team or direct relationship. A group badge shows how many distinct known Project entries include each recipient. Different recipients on different entries do not mean that every recipient has access to the whole group. These counts describe the loaded entries. **No Teams or Identities added** describes saved sharing settings, not every possible source of access. Review lists **Devices included after this update** from the access preview. Expand a device to see its Project entries. A device included for one entry is not included for every affected entry. **Sharing settings saved** confirms the settings were saved. It does not confirm delivery, which happens through background sync. For a new teammate, open **Sharing → Create an invitation**. Choose Team onboarding for ongoing collaboration, or **Share exact Projects** to invite one Identity without giving them Team membership. Review the Projects and existing-memory counts before sending the invitation. An invitation is single-use; accepting it sets up the recipient's device and starts delivery. Check **Devices** for ownership and availability, then **Health** for sync problems. A device being offline does not remove its access. To add another device for someone who already has an Identity, create an **Add device** invitation for that Identity in Sharing. Review the direct and Team Projects that the new device will receive. On **Devices**, choose **Rename device**, enter a friendly name, and choose **Save name**. This updates each active coordinator group where the device is enrolled; a partial failure leaves the local name unchanged so you can retry. Names for devices without coordinator enrollment stay local to this installation. **Change Identity** reassigns a configured device to a *different* Identity; it does not rename it or change Project access. If there is no different active Identity, use the invitation flow to add a new person or device instead. ## When do I need a Space? You do not need to choose a Space to use the normal Project sharing flow. Spaces are the underlying access boundaries that keep different sets of memories apart; they still exist for sync and older setups. **Advanced Space assignment** in a Project's details changes its mapping and needs individual review when workspaces are ambiguous. Use it only when maintaining an existing mapping or troubleshooting a boundary. A coordinator group is for discovery and administration; being in one does not grant access to a Project. **Only me** memories stay local even when their Project is shared. Grouped rows count **Project entries**. Entries can include a repository, recorded workspace paths, and Projects received from other devices. The count does not tell you how many worktrees currently exist on disk. **Show entries** expands them directly below the Project header, before Advanced Space assignment. If you see **Project match needs review**, choose **Review entries**, check the remote or recorded path, and use the individual entry's Space controls. **Project matches needing review** lists the checks for each entry. This review concerns Project attribution and is separate from Identity enrollment. Received entries remain read-only on this device. For setup recovery and advanced compatibility details, see the [user guide](user-guide.md#projects-sharing-devices-and-health).