← Resources
- No training on your content, by default and contractually. Claude Team is a business account: Anthropic doesn’t train on your content, by default and in the contract. (Personal accounts don’t carry that contractual no-training guarantee — that’s why the HR team works on Team, not on personal logins.)
- Most HR data isn’t HIPAA-PHI. HIPAA-PHI is health data held by a covered entity — the company’s group health plan. The employer-held HR records the team actually works with (offers, JDs, comp narratives, policies) fall under the employment-records exception and are governed by ADA, GINA, and state privacy law, not HIPAA. Classify first, and most of the “we can’t use AI” worry resolves.
- The one carve-out is genuine PHI. Team is not BAA-covered — a BAA covers only the first-party API and HIPAA-ready Enterprise. So if there’s a workflow with real plan-side PHI, it doesn’t run on Team; it goes to HIPAA-ready Enterprise or the API on AWS Bedrock. That’s a company / compliance / IT decision, not the HR team’s — and most HR work never touches it. (See the surface map and the genuine-PHI path.)
- Scope it before you start. The data-classification worksheet sorts HR data into plan-side PHI, sensitive-HR / PII, and general business data — so Legal can see exactly what runs on Team and what doesn’t.
- Scoping is for your benefits and employment counsel to confirm — this isn’t legal advice.
- Team is a fixed, bundled per-seat bill. Usage is bundled into the seat — a Standard seat runs about $20/seat/month annual ($25 if billed monthly; 1.25× Pro usage), verified June 2026 — so you know the number before the month starts. No usage billed at API rates, no monthly surprise. For an HR team of, say, 8, that’s a known line item, not a variable one.
- One heavy user can’t drain the team. Limits are per member — the analyst living in Claude Code all day doesn’t eat into anyone else’s usage. Mix Standard and Premium seats if one or two people need the heavier allowance.
- Spend caps are a setting, not a hope. Team includes org- and user-level spend caps. The ceiling is configured up front; the bill can’t exceed it.
- This is the opposite of Enterprise’s usage model. Enterprise decouples the seat from usage and bills tokens at API rates — the real variable an org has to model. The HR team doesn’t take that on: bundled Team seats keep the team’s bill flat and predictable. (See the cost model and the plan decision guide.)
- Yes — on Team, without Enterprise. Claude Team already includes SSO with domain capture, central billing and admin, and Primary Owner / Owner / Member roles. The HR team’s workspace plugs into your existing identity provider; no Enterprise contract is needed for the team to run cleanly.
- De-provision is one place. Remove someone in the IdP and their Claude access ends with it. Offboarding doesn’t become a new manual step for HR or IT.
- Surface control. Sanction the one Team workspace and keep personal accounts out of company work. The surface map says which surfaces are covered, which train on content, and which are admin-visible.
- The company-wide controls are Enterprise — and that’s IT’s project, not the HR team’s. SCIM, audit logs, the Compliance API, IP allowlisting, custom data retention, and fine-grained RBAC live on Enterprise. Those matter for a full-org deployment — identity at scale, security, procurement, the contract — which IT leads. An HR team adopting Claude for its own work doesn’t wait on it.
- Pilot before you scale. One function — the HR team — on Team is exactly the controlled pilot a later company-wide rollout would want to learn from.
Anthropic changes plan structure, BAA terms, and surface coverage often — re-verify at support.claude.com and claude.com/pricing at decision time. Legal points are for your counsel to confirm; this isn’t legal advice.
Why it works
HR adopts on Team with the answers already in hand.
The HR team doesn’t need an org-wide AI program to start using Claude for its own work. On Team, the finance, legal, and identity questions all resolve at the team’s own scope — a bundled bill, no training on content, and identity that plugs into your IdP — with genuine PHI as the one carve-out that goes to IT.
So when Legal, Finance, or IT asks, each has their own answer in front of them. The decision to let the HR team adopt Claude on Team doesn’t wait on a company-wide rollout — that’s a separate, later, IT-led project.
The AI-for-HR Sprint
The kit is the product of the Sprint.
A Sprint produces this kit against your real data, plan, and identity stack — each cut specific to your company, not a template.
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 first one’s free.