What you will be able to do
- State which plans can create and share projects, and what that means for collaboration
- Choose between Can view and Can edit for each member of a shared project
- Use individual, bulk and organisation-wide sharing, and find shared projects
- Predict what happens to existing shares when an admin turns sharing off
1.Who can create projects, and who can share them
Every Claude user can create projects, including free users, though a free account is limited to five. Being able to create a project is not the same as being able to share one. Sharing is documented only for Team and Enterprise plans, where a project can be opened to other members of the organisation.
This has practical consequences. Someone on a free, Pro or Max plan can build a project with carefully written instructions and a well-organised knowledge base, but the sharing features described here are not available to them. If the scenario is "the team needs to work from the same context", check the plan first: the documented way to give several people the same project is a Team or Enterprise organisation.
A support team lead creates a Claude Project and wants Claude to always answer in a formal tone and respond as a senior support engineer for every conversation in that workspace, without repeating those directions in each chat. What should the lead configure?
Correct answer: A — Set project instructions defining the tone and role, since these apply automatically to every chat
- A. Correct. Project instructions are built specifically to establish behavioral guidelines, such as tone and role, that Claude applies to all chats within that project.
- B. Incorrect. A file named like instructions is still treated as knowledge base content, not as project-level behavioral instructions.
- C. Incorrect. Repeating guidance in every chat defeats the purpose of project instructions, which persist automatically across chats.
- D. Incorrect. Creating a project per tone combination is unnecessary overhead when a single project's instructions field already covers this need.
2.Can view versus Can edit
When a creator shares a project, they give each member one of two permission levels. The difference matters because instructions and knowledge shape every chat in the project. Anyone who can change them changes Claude's behaviour for all members.
| Capability | Can view | Can edit |
|---|---|---|
| See project contents, knowledge and instructions | Yes | Yes |
| Chat within the project | Yes | Yes |
| Modify project instructions and knowledge | No | Yes |
| Add or remove members and update member settings | No | Yes |
Because view access still lets people chat, most people who only need to *use* the project's context can get Can view. Can edit is for the people responsible for maintaining the instructions and knowledge. With edit access a member can also add and remove members, so granting it widely hands out control over who has access, not just over the content.
Any of them can change the instructions and knowledge that every member's chats rely on, and can add or remove members. One careless edit changes Claude's behaviour for the whole group. Can view would have let them chat without that risk.
A marketer discusses a campaign brief with Claude in Chat A inside a project, but Claude does not recall those details when the marketer opens a new Chat B in the same project. What most likely explains this?
Correct answer: A — The brief was only discussed in Chat A and was never added to the project's shared knowledge base
- A. Correct. Context is not shared across chats in a project unless it has been added to the project knowledge base; discussion in one chat alone stays local to that chat.
- B. Incorrect. There is no documented per-billing-cycle cap on the number of chats within a project that would explain this behavior.
- C. Incorrect. Plans do not restrict a project to a single chat; multiple chats within one project are expected and supported.
- D. Incorrect. Re-saving project instructions has no bearing on whether one chat's conversation content is visible to another chat.
Sources2
3.How to share, and where shared projects appear
To share, open the project and click Share project next to its name. Add people by name or email, or paste a list of email addresses to share in bulk, then choose a permission level for each person and click Share. There is also organisation-wide sharing, which makes a project available to everyone in the organisation, either when you create it or later. A creator can therefore share with specific members only, or later make a project that started out private visible to the whole organisation.
Access can be managed after sharing. The sharing menu lists every current member and their permission level. You can change a member's role there, and the project creator can remove someone by clicking their current role and selecting Remove access. People who receive a share get an email notification. The Projects page has three tabs: Your projects for projects you created, Organization for projects shared with the whole organisation, and Shared with you. If you can't find a project, check all three.
4.Admin controls over sharing
Organisation owners set the limits for sharing. Owners can turn off project sharing for the whole organisation, or on Enterprise plans for specific roles. Turning off Share projects also turns off Public projects. Separately, if an Owner or Primary Owner disables public projects, organisation-wide sharing is unavailable both when creating a project and afterwards. This is why the create screen offers sharing with the broader organisation only where administrators have enabled it.
Turning sharing off does not revoke anything. Users can no longer share projects with new users or groups, but existing shares stay in place. If the goal is to remove someone's access to a particular project, the switch that disables sharing will not do it. The creator has to remove that member's access in the project's sharing menu.
Sources2
5.Project memory and moving chats between projects
Memory is separate from project knowledge. Memory is on by default for Free, Pro and Max plans on the web, Claude Desktop and Claude Mobile. On Team and Enterprise plans it is available when an owner has enabled it. Each project keeps its own memory, separate from your chats outside projects.
You can move a standalone chat into a project with Add to project from the dropdown next to the chat name. The same menu lets you move chats between projects or remove them from a project. For Team and Enterprise plans that use memory, this is how you control what goes into a project's memory. If an unrelated chat was started in a project by mistake, Remove from project moves it to your non-project memory instead.
Sources1
Exam traps
Each one states something that sounds right. Open it to see what is actually true.
1.Any paid plan, including Pro, lets a project's creator invite collaborators into the project.Why is that wrong?
Project sharing is documented only for Team and Enterprise plans. On other plans, creating a project does not give you a way to share it.
2.Can edit is a harmless default because everyone uses the project the same way.Why is that wrong?
Can edit lets a member change the instructions and knowledge every chat depends on, and add or remove members. Can view still allows chatting in the project.
Covered in Can view versus Can edit
3.When an owner turns off project sharing, every existing share is revoked immediately.Why is that wrong?
Turning sharing off blocks only new shares. Existing shares remain until the creator removes them.
Covered in Admin controls over sharing
Sources
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.
“Free users can create a maximum of five projects.”
↩︎ Who can create projects, and who can share them“To remove access: The project creator can click on the member's current role and select "Remove access."”
↩︎ How to share, and where shared projects appear“If you can't find a project, check all three tabs.”
↩︎ How to share, and where shared projects appear“Memory is on by default for Free, Pro, and Max plans on the web, Claude Desktop, and Claude Mobile.”
↩︎ Project memory and moving chats between projects“Each project has its own memory, kept separate from your non-project chats.”
↩︎ Project memory and moving chats between projects - 2.
“For users on Team and Enterprise plans, projects can be shared with other members of your organization”
↩︎ Who can create projects, and who can share them“Can view: Members can see project contents, knowledge, and instructions, and chat within the project, but cannot edit it.”
↩︎ Can view versus Can edit“Can edit: Members can modify project instructions and knowledge, add/remove members, update member settings, and actively contribute to the project.”
↩︎ Can view versus Can edit“Organization-wide sharing: Make projects available to everyone in your organization either when creating the project or afterward.”
↩︎ How to share, and where shared projects appear“Admin controls: Owners can turn off project sharing for your organization, or on Enterprise plans for specific roles.”
↩︎ Admin controls over sharing“Turning off Share projects also turns off Public projects.”
↩︎ Admin controls over sharing“When sharing is off, users can't share projects with new users or groups, and existing shares stay in place.”
↩︎ Admin controls over sharing“For users on Team and Enterprise plans, projects can be shared with other members of your organization”
↩︎ Exam trap 1“Can edit: Members can modify project instructions and knowledge, add/remove members, update member settings, and actively contribute to the project.”
↩︎ Exam trap 2“When sharing is off, users can't share projects with new users or groups, and existing shares stay in place.”
↩︎ Exam trap 3