Who can share, and with whom
| Plan | Share Projects? |
|---|---|
| Free, Pro, Max, Ultra | No |
| Team | Yes, within the organization |
| Enterprise | Yes, within the organization |
Sharing happens inside your Claude organization. You add people in one of three ways:
- By email address, one colleague at a time.
- In bulk, several people at once.
- With the whole organization.
The two permission levels
| Right | What the person can do |
|---|---|
| Can view | Read the Project and chat in it, using its knowledge and instructions |
| Can edit | Everything above, plus change instructions, knowledge, members and settings |
A sensible default for most teams: one or two people with Can edit who own the Project’s instructions and files, everyone else on Can view. That keeps the instructions stable while the whole team benefits from them.
The organization owner can turn Project sharing off. Explicit shares remain, but public Projects become private and access based only on organization-wide visibility is removed.
How to set up a team Project that works
- Create the Project and write instructions that hold for everyone: tone, format, what to check.
- Add the knowledge the team needs every time, kept small and current. See how Claude Projects work for how Claude handles large knowledge sets.
- Share it with the right people, at the right level.
- Agree who updates the files when the source documents change.
What works alongside shared Projects on Team
A shared Project is not the only team-wide setting on the Team plan. Admins can also set organization-wide instructions that apply to everyone, roll out skills to the whole team, and connect tools such as Google Drive, GitHub, Microsoft 365 and Slack. A practical split: put what holds for the whole company in the organization instructions, what holds for one client or product in the Project, and keep the Project knowledge to the documents people actually need.
The misunderstanding: sharing a Project is not sharing memory
When a team shares a Project, they share the instructions and files. They do not share what each person taught Claude along the way. Memory in Claude is built per member from their own chats, and Anthropic’s help pages describe no way to hand it to a colleague. So if one colleague corrects Claude ten times on how your proposals should look, that lesson sits in their memory, and the next colleague runs into the same mistakes. The only way to share it is to write it into the Project instructions by hand. More on how memory works per person in does Claude have memory.
The same holds outside Claude. Colleagues who work in ChatGPT, Copilot or Cursor see nothing of the Project. Sharing in Claude requires a Team or Enterprise seat for everyone involved; see Claude Team pricing per seat.
Where Bombos fits
A shared Project shares what someone wrote down. Bombos is a plugin that gives every AI tool your team uses one shared memory, including the rules learned from corrections, so the lesson one colleague teaches reaches the next, in Claude and in ChatGPT, Copilot, Cursor or your own agents. One person can try it first for their own agents.
Related questions
Can I share a Claude Project from a Pro account?
No. Sharing is only available on Team and Enterprise plans.
What happens to existing shares if the owner turns sharing off?
According to the help center, explicit shares remain, public Projects become private, and access based only on organization-wide visibility is removed.
Can colleagues with Can view rights chat in the Project?
Yes. Can view allows reading and chatting; changing instructions, knowledge, members or settings requires Can edit.
Can I share a Cowork session instead?
No. Cowork sessions cannot be shared, but artifacts from them can.
