Anthropic · Technologies
Claude for Enterprise
Claude for the whole organisation, governed.
Claude for Enterprise puts Claude, Claude Code and Cowork in every seat with the controls a large organisation needs: single sign on, SCIM provisioning, audit logs, custom retention and a Compliance API your security team can wire into their monitoring. We plan, deploy and govern it so the spend turns into capability.
WORKSPACE HEALTH · EXAMPLE ORGANISATION
AREA
SIGNAL
OWNER
STATUS
SSO-SCIM
Identity connected
IT
HEALTHY
Audit-Logs
Streaming to SIEM
Security
HEALTHY
Retention
Policy set
Legal
HEALTHY
Connectors
Rollout scope
IT
REVIEW
Shadow-AI
Personal accounts
Security
RISK
Sample organisation
healthy · review · risk
In plain terms
Most organisations already use Claude. Far fewer govern it.
Your people adopted AI before the policy existed. Enterprise brings it under control. Here is what changes.
Without it
- Staff pasting work into personal AI accounts
- No record of who used AI for what
- Leavers keeping access nobody remembered to revoke
- Every team inventing its own rules
With it
- One governed workspace under your identity system
- Audit logs and a Compliance API for your security tooling
- Joiners and leavers handled by SCIM automatically
- One policy, enforced by the platform
What CG TECH can do with Claude for Enterprise
The work, broken into the parts that matter.
An AI workspace IT actually controls
Single sign on with domain capture, SCIM provisioning and role based access, so joining, moving and leaving staff are handled by your identity system, not a spreadsheet.
an AI workspace IT controls
Evidence, not assurances
Audit logs capture user actions and system events, the Compliance API streams usage data into your security tooling, retention is configurable and HIPAA-ready agreements are available where needed.
compliance evidence on tap
Built for heavy, real work
An expanded 500K context window for the long documents and large codebases, usage billed on what you actually consume, and IP allowlisting for locked down networks.
capacity for serious work
From licences to habits
Use case selection, training and usage analytics, so six months in you can show the value rather than guess at it.
adoption you can measure
How an engagement runs
From shadow AI to a governed rollout, step by step.
01
Assess
We audit current AI use, including the shadow AI you do not know about.
02
Design
Identity, retention, connectors and policy set deliberately.
03
Roll out
Seats provisioned, teams trained on real use cases.
04
Embed
Usage reviewed, policy tuned, value measured honestly.
Questions we hear a lot
Common questions about Claude for Enterprise
What is Claude for Enterprise?
Claude for Enterprise puts Claude, Claude Code and Cowork in every seat with the controls a larger organisation needs: single sign on, SCIM provisioning, audit logs, custom retention and a Compliance API your security team can connect to their own monitoring.
Is our data used to train Claude?
No. Your organisation’s data is not used to train Claude models by default, and retention is configurable to your policy.
When is Enterprise worth it over Team?
When you need SCIM, audit logs, the Compliance API, custom retention, IP allowlisting or the larger context window, or when you are past 150 seats. There is now a self serve path from 20 seats, and we help you make the call on your actual numbers.
How is Claude for Enterprise licensed?
A per seat fee plus usage billed at API rates for what your people actually consume. That rewards well governed rollouts, and we model the total cost during discovery.
Can our security team monitor usage?
Yes. Audit logs cover user actions and system events, and the Compliance API gives programmatic access to activity data so it can flow into the monitoring you already run.
What is the Compliance API?
It gives real-time programmatic access to Claude usage data and content, so AI use can be evidenced through your own systems rather than described in a policy. It is the difference between believing your controls work and being able to show it.
What has to be decided before we roll it out?
What staff may and may not put into it, in plain language, and who approves exceptions. The technical setup takes days. Getting agreement on acceptable use is what actually sets the timeline, and skipping it causes the problems later.
How do we know whether it paid off?
Decide the measure before you buy. Pick the handful of tasks it should speed up, note roughly what they cost in time now, and look again at ninety days. Without that, the renewal conversation comes down to who liked it.
Ready when you are
Rolling out Claude properly? Let us talk.
A discovery session maps your use cases, your risks and your quick wins. You keep the plan either way.
What to expect
- A consultant replies within 4 business hours
- Session booked to understand your requirements
- We will provide you with a fixed price quote