As of August 1, 2025, Anthropic enabled project permissions and sharing on Claude's Team and Enterprise plans. If your organization is on one of those plans, projects can now be shared across the organization with permission controls instead of staying siloed with the person who created them. If you're not on Team or Enterprise, this release doesn't mention your plan. Details are in Anthropic's Organization-wide sharing documentation.
Deep Dive: What actually changed
On August 1, 2025, Anthropic's release notes announced that project permissions and sharing are now enabled for Team and Enterprise plans.
That single line carries a real shift. Projects in Claude are workspaces where a person collects the context, files, and instructions they use repeatedly. The fact that Anthropic had to "enable" sharing implies the previous state: projects on these plans effectively lived with whoever created them. Now, per the release notes, sharing comes with permissions — meaning access is controlled, not all-or-nothing — and Anthropic points to its "Organization-wide sharing" documentation, which signals the sharing model operates at the organization level, not just person-to-person.
Why this matters for ops and business teams
When projects can't be shared, every team member rebuilds the same setup: the same background documents, the same standing instructions, the same context. That work is invisible until someone leaves and their carefully built project leaves with them. Organization-level sharing with permissions changes projects from personal tooling into something closer to shared team infrastructure — a project one person sets up well can become the version everyone uses.
The permissions piece matters just as much as the sharing piece for admins: sharing without controls would be a governance problem in an enterprise setting. The release notes explicitly pair the two.
What's the catch?
One clear scope limitation, stated directly in the source: this applies to Team and Enterprise plans. The release notes don't mention other plans, so if your organization uses Claude on a different tier, don't assume this applies to you.
How to use this in your day-to-day work
The release notes are brief and don't include step-by-step setup instructions, so we won't invent any. What the source honestly supports:
- Confirm your plan. This is enabled for Team and Enterprise plans. If you're an admin, that's the first thing to check.
- Read Anthropic's Organization-wide sharing documentation. The release notes point there directly for how sharing and permissions work in practice — that's the authoritative reference for setup.
- Identify projects worth sharing. If people on your team have independently built similar projects (for example, a project with your standard company context or recurring process documents), this change is the mechanism to consolidate that duplicated effort — once you've reviewed the permission options in Anthropic's docs.
For the specifics of who can share what and how permissions are configured, Anthropic's own documentation (linked from the release notes) is the source to follow. This site is independent and not affiliated with Anthropic.
claudedetails.com is an independent publication and is not affiliated with, endorsed by, or sponsored by Anthropic. "Claude" is a trademark of Anthropic, PBC, used here for identification purposes only. Product details can change — always confirm specifics on Anthropic's own site before making decisions based on this post.
More in Enterprise & Admin
Enterprise & AdminWhat changed
Aug 12, 2026If your organization is on Claude's Max, Team, or Enterprise plan, you can now ask Claude to search your past conversations instead of re-explaining context in every new chat. To use it, simply prompt Claude to look for a previous conversation on a topic. Free and Pro users are not mentioned in Anthropic's announcement, so this appears limited to those three plans.
Read more →Enterprise & AdminWhat changed
Aug 10, 2026If your organization handles protected health information and uses Claude Enterprise or the Claude Platform (API), you no longer need to go through Anthropic to get HIPAA readiness set up. As of July 14, 2026, an eligible admin can handle it directly: review the Business Associate Agreement (BAA), download the implementation guide, and enable the HIPAA configuration, all in one flow inside the product. If you don't work with health data, this change doesn't affect you. If you do, the practical step is to have your admin check whether they're eligible to run this flow in your Claude admin settings, and to loop in your compliance or legal team before accepting the BAA, since it's a binding agreement. This applies to both Claude Enterprise and the API platform.
Read more →Enterprise & AdminWhat changed
Aug 10, 2026If your organization uses Claude on an Enterprise plan, Claude can now remember relevant context from your chats instead of starting every conversation from zero, and it generates a memory summary of what it has retained. This matters most if you find yourself re-explaining the same background — your team's terminology, ongoing projects, recurring context — at the start of each new chat. If you're not on an Enterprise plan, this announcement doesn't apply to you yet based on what Anthropic has published. For conversations you don't want feeding into memory — sensitive HR matters, one-off questions, anything confidential — use an incognito chat, which excludes that conversation from Claude's memory. The memory summary gives you a way to see what Claude has actually retained, rather than guessing.
Read more →
ClaudeDetails