Claude Governance

How to roll out Claude without leaking confidential data.

If you handle sensitive data, the question is not whether Claude is safe. It is whether you have put the right data in the right workspace, controlled who can see it, and can prove it. Team and Enterprise do not train on your content by default, and admins can cap what each person spends. This guide is the governance reference for the people who answer to compliance, finance, and the board.

Last updated October 2026

Quick answers

What comes up first

Our IT team wants a security review before anyone uses Claude. What do they get?

A plan-by-plan control table, a four-tier data classification and a six-part AI use policy, all on this page. SCIM, audit logs, the Compliance API, custom data retention and a HIPAA-ready offering are Enterprise-only, and single sign-on is on both plans.

Is our confidential deal data safe in Claude?

It depends on which data goes into which workspace. Team and Enterprise do not train on your content by default, and restricted data such as material non-public information stays out of any general workspace.

Can we use Claude with regulated data?

Your counsel decides what your regulator requires. On the Claude side it comes down to classification, access controls and human review, and a HIPAA-ready offering is Enterprise-only.

Our staff already use personal AI accounts. What do we do?

Block consumer accounts for work and give everyone an approved company workspace. A written policy alone does not stop it, so pair it with DNS, proxy or endpoint controls.

If Claude gets something wrong, who is accountable?

A named person reviews and owns every AI-assisted output before it leaves the firm. Nothing AI-touched reaches a client, investor or counterparty without that sign-off.

Can one person or one agent run up the bill?

Not past a limit you set, give or take one request. Admins set an organization limit and a per-user limit, and a user who reaches theirs is stopped until the limit resets or an owner raises it.

Should we start on Team or Enterprise?

Team, unless a contract or a regulator asks for audit logs, SCIM, custom data retention or a HIPAA-ready offering. Those four are Enterprise-only, checked October 13, 2026.

Start here

The biggest objection is already answered

By default, Anthropic does not train its models on the inputs or outputs of paid commercial plans, Team or Enterprise. That is a contractual commitment, and it is the same answer on both tiers. A Data Processing Addendum is included automatically with both. The one way commercial data enters training is if your organization explicitly opts in, or if a user clicks the thumbs up or down feedback button, and an admin can switch that button off across the organization.

Consumer tiers (Free, Pro, Max) are a different product with different terms, and they are not fit for business or regulated data. Block them. That settles the model-training question. The work that remains is classifying your data, controlling who reaches what, proving what happened, and getting people competent enough to follow the policy. The rest of this guide covers it.

The floor

The minimum defensible floor for business data is Team. The floor for regulated or audited governance is Enterprise. A personal consumer account fails on every count: no DPA, longer retention exposure, a likely breach of your own data policy, and human review of flagged content.

Step one

Classify your data first

Governance only works if you know what you are protecting. Four tiers cover almost every team. Decide what belongs in each, then the rest of the controls follow.

Public
Already public. No harm if disclosed.
Marketing material, published strategy, press releases, public filings.
Fine on any paid commercial tier. Still review output before publishing.
Internal
Non-public, but low harm if seen.
Internal templates, training material, non-sensitive ops docs, general research questions.
Acceptable on Team or Enterprise under the commercial terms.
Confidential
Material business harm if it leaks.
Financial models, customer or investor communications, deal and diligence findings, performance data.
Only on a properly configured commercial tier, with access controls and a defined use case. Many regulated firms gate this behind Enterprise. Watch for NDA or data-room clauses that bar AI ingestion.
Restricted
Legal, fiduciary, or regulatory exposure.
Material non-public information, anything behind an information barrier, insider material, regulated personal data your policy forbids.
Default-deny. Never enter into a general Claude workspace.

The diagnostic question

The fastest way to find out where a team really stands: ask how today’s policy would stop someone from pasting a confidential document into a personal AI account at home. If the answer is that it would not, the policy exists on paper only.

Step two

Pick the tier on governance, not headcount

Both tiers carry the no-training commitment and a DPA. What separates them is control. Team is fine for a small pilot. The moment you need SSO with your identity provider, audit logs into a SIEM, custom retention, or roles that enforce an information barrier, you want Enterprise. One thing to plan for: the Team-to-Enterprise migration is a one-way door, so if you expect to need Enterprise within a year, start there.

No model training on your content
Yes
Yes
Data Processing Addendum (DPA) included
Yes
Yes
Single sign-on (SSO)
Google or Microsoft only
Full SAML 2.0 / OIDC (Okta, Entra ID, others)
SCIM provisioning
No
Yes
Audit logs
No
Yes
Compliance API (feed your SIEM)
No
Yes
Analytics API (adoption metrics)
No
Yes
Role-based access for information barriers
Admin vs member only
Fine-grained custom roles and groups
Custom data retention
No (30-day default)
Yes (configurable, 30-day minimum, auto-delete)
Customer-managed encryption keys
No
Yes
IP allowlisting / network controls
No
Yes
US-only inference
No
Yes (usage billed at 1.1x API rates)
HIPAA-ready option + BAA
No
Yes (sales-assisted)
Seats
2 to 150
20 seats self-serve, 50 sales-assisted

Want the full pricing and billing breakdown? Read the complete Team vs Enterprise comparison.

Spend control

How to keep the Claude bill a number you chose

Set an organization limit and a per-user limit before you turn on usage credits. With both set, the usage-credit part of your bill has a ceiling you picked, give or take one request. Every figure below was checked against Anthropic’s own pages on October 13, 2026.

What is the base bill?
Team$25 per standard seat per month, or $20 billed annually. $125 per premium seat per month, or $100 billed annually (US pricing). Usage limits are per member, not pooled.
Enterprise$20 per seat per month, billed annually. The seat fee covers access only, and every token is billed separately at API rates.
Who sets the limits?
TeamOwners and Primary Owners turn on usage credits, then set a monthly limit for the whole organization and a monthly limit for each user.
EnterpriseOwners and authorized roles set limits for the organization and for individual users. A user cannot exceed their own limit or the organization limit, whichever is lower.
What happens when someone hits a limit?
TeamWith usage credits off, that person waits for their allowance to reset and everyone else keeps working. With credits on, they keep working until their spend limit, then their credits pause until the end of the month.
EnterpriseSelf-serve: usage stops for that user even if credits remain, until an owner buys credits or raises the limit. Sales-assisted: usage stops until the next billing period begins or an owner raises the limit.
Do you pay before or after?
TeamOwners pre-purchase usage credits, with optional auto-reload when the balance falls to a level they choose.
EnterpriseSelf-serve: usage is bought up front in credits that draw down. Sales-assisted: usage is billed monthly in arrears, and the invoice shows usage per user.
Where do you see spend?
TeamA spend report in organization analytics shows estimated spend per user and per model, with CSV export. It covers usage-credit spend and refreshes daily with a one-day delay, so the limit protects you and the report explains afterward.
EnterpriseOrganization settings, then Usage, shows month-to-date spend per member and limit status, and the credit balance on self-serve. Spend limit notifications fire as users or the organization approach a threshold.
Can a limit be switched off?
TeamYes. An owner can set the organization limit to unlimited. Do not.
EnterpriseAn owner can set a limit to unlimited, but billing for usage cannot be disabled. Do not set unlimited.

One caveat from Anthropic’s usage-credits article: a limit can be exceeded slightly. The check runs before each request, so the request that crosses the line still completes and every request after it is blocked.

Runaway agents and Claude Code

The bill that surprises people comes from autonomous work, not from chat. Four facts from Anthropic’s Claude Code documentation explain it.

What a Claude Code user costs

Anthropic reports that Claude Code averages about $13 per developer per active day and $150 to $250 per developer per month across enterprise deployments, with costs below $30 per active day for 90% of users. Its advice is to start with a small pilot group and measure a baseline before wider rollout.

Why autonomous work costs more

Agent teams use about 7x more tokens than standard sessions when teammates run in plan mode, because each teammate keeps its own context window. A scheduled task fires on its interval even while a session sits idle, and sends the full context each time.

What caps it on Team

Claude Code draws from the same per-seat allowance as chat and Cowork, and that allowance is the default ceiling. Usage credits, if you turn them on, cover Claude, Cowork and Claude Code, so your organization limit and per-user limits cap them too.

What caps an unattended run

For scripted runs, claude -p takes --max-budget-usd and --max-turns. Both apply to print mode only, the budget is checked against a client-side estimate that can differ from your bill, and spend can pass the cap, so leave headroom. On the Claude Console API, workspace spend limits cap Claude Code spend.

Our recommendation

Before anyone gets usage credits, set an organization limit and a per-user limit, and never set unlimited. Pilot Claude Code with a small group, read the spend report, and set per-user limits from that baseline.

Step three

Write a six-part AI use policy

A workable policy is short, specific to your actual Claude setup, and different for different roles. Keep it to six parts, and back it with the technical controls above. A policy with nothing enforcing it is the stage-one trap.

1. Approved tools and accounts

Name the approved environment explicitly: the company's Claude Team or Enterprise tenant only. Block personal accounts and consumer tiers for any work. The most common failure is people using the wrong workspace, not a model flaw, so train people to recognize which account they are in.

2. Acceptable use

List the workflows that are approved: research on public information, drafting internal memos from non-sensitive inputs, summarizing public documents, formatting, editing, code. Tie each one to a data tier so the line is concrete.

3. Prohibited use

No restricted data. No material behind an information barrier. No regulated personal data your policy forbids. No data barred by an NDA or data-room clause. And no AI as the final decision-maker on a customer or investment outcome.

4. Human in the loop

Require a named human to review and own any AI-assisted output before it is used. Distinguish a cursory read from a substantive review, and write down which one is required for which kind of work.

5. Disclosure norms

Decide where AI use is disclosed. A working line: AI as an internal tool assisting a reviewed work product usually needs no disclosure; AI-generated content sent to a customer, investor, or counterparty without human review does. Keep any public claims about your AI capabilities accurate.

6. The drafts-only rule for anything outbound

AI output is a draft until a human reviews, edits, and signs off. Nothing AI-touched reaches a client, an investor, a board, a counterparty, or a regulator without that step. For regulated firms this is the single most important operational rule, because outbound communications carry the most exposure.

Where teams really are

The four stages of control

Most teams have a written policy and assume it protects them. It does not enforce itself. Real governance moves through four stages, and very few teams have reached the third. The fourth is the one an auditor asks for evidence of.

Stage 1

Written policy only

A document exists and nothing enforces it. Most teams are here. A policy does not stop a junior from pasting a confidential file into a personal AI account at home.

Stage 2

Technical controls on access

DNS, proxy, or endpoint controls restrict which AI tools people can reach, so consumer accounts are blocked and the approved tenant is the path of least resistance.

Stage 3

Data loss prevention tied to classification

DLP is wired to your data classification, so an employee cannot paste or upload classified data into even an approved tool. It requires a real classification program first.

Stage 4

Competence on the record

Controls are not the only thing holding the line. People know which account they are in and what each data tier means, and you can show who was trained and when. ISO/IEC 42001 asks for that evidence and the EU AI Act puts an AI literacy duty on anyone deploying these tools.

For Microsoft shops

The Microsoft 365 connector, in plain terms

If your company runs on Microsoft 365, this is the integration that matters, and it was built with governance in mind. The connector to Outlook, SharePoint, OneDrive, and Teams is read-only. It cannot send mail, create documents, or post in Teams. It uses per-user sign-in, so Claude sees only what the signed-in person can already open, and it respects sensitivity labels, folder permissions, and your Conditional Access rules. Every retrieval lands in your Microsoft 365 audit log.

Turning it on takes two deliberate steps: an organization owner enables the connector, then a Microsoft Entra global administrator grants consent. Until both happen, no one has access. You can scope it to a pilot security group first, and you can revoke any individual capability (mail, files, SharePoint, Teams) from Entra at any time.

The one sharp edge

SharePoint search uses a tenant-wide read scope. You cannot tell the connector to search only certain sites. Because it still mirrors each user’s own permissions, the control is on the Microsoft side: anyone who should not reach a walled site simply should not have access to it in the first place. Lock down third-party app consent too, so individuals cannot quietly self-register a connector through a personal account.

The questions you will be asked

What compliance, finance, and the board will want to know

Short, accurate answers to the questions that come up in every governance conversation.

Does Anthropic train on our data?

Not on paid commercial plans. By default, Anthropic does not train on the inputs or outputs of Team or Enterprise, and this is a contractual commitment in the commercial terms. The exceptions are if your organization explicitly opts in, or if a user submits thumbs up or down feedback, and admins can disable that feedback button across the organization. Consumer tiers (Free, Pro, Max) are different and are not appropriate for business data.

Where does our data go, and is there an EU option?

First-party Claude (Team and Enterprise chat) processes and stores in the US, and Enterprise offers a US-only inference control. There is no first-party EU workspace today. If you need EU data residency, the route is Claude through AWS Bedrock or Google Vertex AI in EU regions, which shifts the primary processing contract to AWS or Google. Settle this with counsel if you have EU customers or entities.

Who can see what inside our organization?

By default, Anthropic employees cannot read your conversations, with narrow exceptions for your consent or a safety flag. Within your org, chats are private to the user unless shared, and projects can be private or shared. Enterprise adds fine-grained custom roles and groups so you can enforce information barriers. There is no live admin dashboard that reads employee chats in real time on either tier.

What is logged, and can we feed it to our SIEM?

Enterprise only. Audit logs capture user actions, sign-ins, and file and system events as metadata; chat content is not in the audit log. The Compliance API gives programmatic access to the activity feed plus chat and file content and feeds tools like Splunk, Sentinel, and Datadog. Team has no audit logs, only an on-demand export by the primary owner. One gap to flag: Claude Cowork activity is currently excluded from audit logs, the Compliance API, and data exports, so OpenTelemetry to your SIEM is the only visibility there.

How long is data retained, and can we control it?

Team keeps a 30-day default with no custom control. Enterprise lets you configure retention (30-day minimum) with automatic deletion when it expires. The API default is shorter. Content flagged for a policy violation can be retained longer. Enterprise's Compliance API also supports scripted deletion for data-subject requests.

Is there a DPA or a BAA?

A Data Processing Addendum with Standard Contractual Clauses is automatically included with Team and Enterprise through the commercial terms, so no separate signature is needed for standard deployments. Free and Pro carry no DPA. A BAA is available on Enterprise as a sales-assisted, HIPAA-ready offering, relevant mainly if a part of your business handles protected health information.

How do we prevent shadow AI and unauthorized connectors?

Block consumer tiers with DNS, proxy, or endpoint controls, and provide the approved tenant so people do not reach for personal accounts. In Microsoft, require admin approval for third-party app consent, audit Entra Enterprise Applications for entries named Claude or MCP, and use Defender for Cloud Apps and Entra Shadow AI discovery. The deeper fix is technical access control plus DLP, not policy alone.

Can we restrict which SharePoint sites Claude can search?

Not at the connector level. SharePoint search through the Microsoft 365 connector uses a tenant-wide read scope, and per-site allowlisting is not supported. Control it on the Microsoft side: because the connector mirrors each user's own permissions, a walled site should simply not be accessible to the person running the query, or you remove the SharePoint scope entirely.

How do we measure adoption without reading anyone's chats?

Enterprise's Analytics API gives aggregated engagement and adoption metrics across the organization without exposing individual chat content. That lets you report utilization to leadership without monitoring conversations. Audit logs are metadata, content requires a deliberate export, and there is no real-time per-message monitoring.

Regulated industries

When the stakes are higher

Some sectors carry exposure that ordinary teams do not. The governance pattern is the same. The default-deny line just moves earlier, and a few questions belong with your own counsel rather than with us.

Investment firms, private equity, and finance

Here the crown-jewel data is not personal information. It is confidential investment data and material non-public information. Treat that material the way you treat an information barrier: never enter it into a general workspace, and mirror your deal-team walls in Claude using Enterprise roles, groups, and private projects rather than one shared org. NDAs and data-room agreements increasingly bar uploading material into AI systems, so check the documents before any diligence content goes near a tool. Securities-law questions, whether something is material non-public information, Regulation S-P timelines, marketing-rule and recordkeeping obligations, and accuracy of any public AI-capability claims all stay with your compliance officer and counsel. This page is operational guidance, not legal advice.

Healthcare and protected health information

If any part of your business handles protected health information, that is Enterprise plus a signed BAA, and a few features are limited under that arrangement. Confirm the current terms with Anthropic before relying on them, and keep clinical and regulatory determinations with your own advisors.

Multi-entity groups and portfolios

If you run several companies, each usually has its own legal entity, its own Microsoft tenant, and often its own compliance perimeter. That points to separate Enterprise organizations per entity with shared policy templates, not one organization for everyone. Several controls (zero-retention arrangements, the Compliance API, customer-managed keys, retention) are set per organization, so plan for a consistent federation rather than a single monolith.

About this guide

The spend-control figures and the seat counts were checked against Anthropic’s published pages on October 13, 2026. The other product facts here were last checked in June 2026 and are drawn from Anthropic’s published documentation, privacy center, and pricing page. Plan terms, retention defaults, seat limits, and feature placement change, so verify against docs.claude.com, trust.anthropic.com, and claude.com/pricing before relying on a specific detail in a contract.

This is operational guidance, not legal or regulatory advice. Determinations about securities law, regulated personal data, fiduciary duties, and recordkeeping belong with your own counsel and compliance officer. Elevate Online is an independent practice and is not affiliated with, endorsed by, or sponsored by Anthropic.

Roll out Claude with the governance already built in

The 90-Day Rollout installs the operating layer and the controls together: classification, access, an AI use policy, and a measurable adoption story your board can read. Book a call to talk through what your team needs.