For an HR team adopting Claude for its own work, the answer is almost always one surface: a sanctioned Claude Team workspace. This map exists because of the surfaces that sit outside it — personal accounts that carry no contractual no-training guarantee, and a narrow set of paths for genuine PHI that are a company and IT decision, not the HR team’s. Read two columns to put HR’s data in the right place: does the surface train on your content, and who can see it.
“Claude” is not one product. The plan and the surface decide whether your data trains the model, who at the company can see it, and whether a BAA covers it. The top row is where the HR team works. The rows below it are the surfaces to keep HR’s data out of, or the narrow exceptions that belong to the company.
| Surface | Trains on your content? | Admin visibility | HIPAA BAA available? | For the HR team |
|---|---|---|---|---|
| Team your sanctioned workspace | No (business default; contractual) | Primary Owner data export | No | This is the surface. Open and sensitive non-PHI HR and business data lives here. |
| Free / Pro / Max personal accounts | No contractual no-training guarantee — verify the current default at support.claude.com | None — personal | No | Keep HR work off these. Personal use only; never company or employee data. |
| Cowork | No (business) | Per plan | No | HR productivity inside the Team plan — but never PHI. No BAA covers it. |
| Enterprise HIPAA-ready | No | Compliance API (full chat/file/project access) | Yes — activate + accept BAA | A company-wide / compliance deployment — IT’s decision, not the HR team’s. |
| First-party API | No | Your own logging | Yes — under BAA | The exception: genuine PHI or product builds, under a BAA. A company/IT path. |
| API via AWS Bedrock | No — data stays in AWS | Your AWS logging | Yes — under your AWS BAA | The exception: health-data-heavy builds; data never leaves AWS. A company/IT path. |
| Console / Workbench | No | n/a | No | API testing only. Not an HR-team surface, not a PHI surface. |
Team is not BAA-covered — only the first-party API and HIPAA-ready Enterprise are. So the single case the HR team’s Team workspace cannot handle is genuine HIPAA-PHI. That’s a company / compliance / IT decision, not the HR team’s, and it points to Enterprise or Bedrock. A signed BAA elsewhere does not reach back to Team or Cowork — it covers the surfaces it names, not the brand.
Personal Free, Pro, and Max accounts carry no contractual no-training guarantee — confirm the current consumer default at support.claude.com before relying on it. Either way, an HR analyst pasting comp data into a personal Claude is a real exposure. The fix is the same as the answer above: give the team one sanctioned Team workspace — no training on content by default and contractually, central admin, spend caps — and keep HR work off personal accounts. Claude Code, the Office add-ins for Excel, Word, and PowerPoint, and the connectors all ship inside that one Team workspace, so the team’s real surfaces sit under the same no-training guarantee.
Anthropic changes plan structure, BAA terms, and surface coverage often — re-verify at support.claude.com and claude.com/pricing at decision time. The PHI and BAA points are for the company’s counsel and IT to confirm; this isn’t legal advice.
For the HR team adopting Claude for its own work, the surface is the Team workspace. Knowing that, the map’s real job is sorting: open and sensitive non-PHI HR data goes into Team; personal accounts and PHI stay out.
The HR team needs exactly one sanctioned surface — Team. The narrow second path, for genuine PHI, is Enterprise or Bedrock, and that’s a company / compliance / IT decision. When IT leads a company-wide rollout, this same map is how HR stays a smart stakeholder.
In a Sprint, the surface map is built against your actual data classification, then turned into the plan recommendation, the acceptable-use policy, and the IT control list.
This is my AI-for-HR practice — one of three I run, alongside Total Rewards and HR Systems. They’re separate practices; you can hire me for any one of them on its own.
Start a conversation →The intro call is free.