Three non-negotiables
01
If you would not email it to a contractor, do not drop it into a chat. Authorization is a gate, not a vibe.
02
Every share click widens an audience by a predictable amount. Know the radius before you press it.
03
Claude drafted it, searched it, or filed it. Your name is still on the decision, the message, and the mistake.
What this section covers
What to share
A practical share / don’t-share matrix for the data that shows up on a normal Tuesday.
Enterprise sharing
Org caps, project permissions, retention, and what your company actually expects.
Ethics
Confidentiality, honesty about AI assistance, and accountability when Claude is in the loop.
Lab: Red-team
Attack one of your real workflows for leakage, then rewrite it safer.
Quiz: Safety & ethics
Ten instructor-led questions before you leave this section.
What you already covered elsewhere
Keep these pages in your back pocket. This section builds on them instead of repeating them.- Sharing, permissions, and what leaves the chat — blast radius, snapshots, training toggles, the quiet channels that leave a session.
- When not to use Claude — permission, human stakes, verifiability, and control as routing gates.
- Failure modes of connected work — plumbing, permission, judgment, and prompt injection when tools can act.
The one-sentence test
Before you paste, upload, connect, or share, answer this out loud:If this left the room the wrong way, who gets hurt, and would I still be allowed to have put it here?If you cannot answer both halves cleanly, the work is not ready for Claude yet.