Skip to main content
On Team and Enterprise plans, Claude is not just your assistant. It is a workplace system with an org boundary, admins, retention rules, and colleagues who can inherit what you set up carelessly. The product still starts private. Your obligations do not get looser because the plan is fancier. They get clearer.

​
What changes on Team and Enterprise

Keep the sharing blast radius in mind, then add these enterprise facts on top:
Org-capped sharing

Chat links and artifacts stop at the organization. They are not a path to the open web from these plans. That reduces one failure mode. It does not authorize sensitive content.

Training defaults

Ordinary inputs and outputs are not used to train Anthropic models by default. That is a privacy win. It is still not permission to paste regulated or NDA’d material.

Admin ceilings

Owners can disable feedback buttons, set retention, govern connectors, and require approvals on write-capable tools. Your personal preference loses to org policy.

Audit reality

Work in Claude can be reviewable later by people who were not in the chat. Write like a future investigator might read it, because one might.

​
Projects are shared workplaces

A project is the right home for recurring work. It is also the easiest place to overshare by accident.
  • Can view lets someone use the project’s knowledge and instructions in chat. They inherit the briefing you built.
  • Can edit lets them change the briefing itself: files, instructions, memory of how the work is done.
  • General access to the whole org is a loudspeaker. Use it for shared tools, not for a deal room.
Before you invite anyone, ask two questions:
  1. Do they need the workshop, or only the deliverable?
  2. If they only need the deliverable, should you share an artifact instead of the project?
If the project contains customer files, credentials history, or strategy that is not theirs, fix the contents before you fix the invite list.

​
Permissions are inherited, not invented

Connectors and Cowork do not grant magic access. They reuse yours. That means three enterprise consequences:
  1. Over-scoped personal access becomes over-scoped Claude access. If your Drive permissions are a junk drawer, Claude inherits the junk drawer.
  2. A clean miss is success. When Claude cannot see a colleague’s private file, the system is working. Do not try to bypass that with a screenshot of something you should not have.
  3. Write tools need a default. Needs approval for anything that sends, deletes, or modifies is the workplace default until a workflow has earned trust. Your admin may already require that.
For the failure families behind these symptoms, stay with Failure modes.

​
Retention is a policy, not a feeling

Enterprise owners can set how long conversations stick around, with a floor measured in days, not vibes. That changes how you should think about “I’ll just delete it.”
  • Deleting your copy is still good hygiene.
  • Org retention and legal holds can outrank your delete button.
  • Do not put something in Claude as a workaround for “I don’t want this in email.” If it should not be written down, it should not be written into a model either.
If you do not know your company’s retention setting, ask once, then stop guessing.

​
What organizations usually expect from you

Exact policy text differs. The expectations below show up in almost every serious rollout: If your company published a Claude use standard, that document wins over this page. This page exists to make the standard feel concrete.

​
Facilitation note

If you are running this page in a live session, pause here and have the participant open three screens before continuing:
  1. Settings → Privacy — training / feedback posture for their plan
  2. Customize → Connectors — what is connected today
  3. One project they already use — who has Can view vs Can edit
The goal is not a scavenger hunt. It is to replace assumptions with the actual configuration they work inside.

Ethical use at work

Confidentiality, honesty, and accountability when Claude is part of the work product.