Today, C1 integrates with Claude's Compliance API. Claude activity data from Claude Enterprise and the Claude Platform now flows into the same governance layer as your identity records.
Companies aren't just evaluating Claude anymore - they're running it. It's embedded across teams and workflows, at a scale that would have seemed ambitious twelve months ago. This rapid shift creates a specific problem: the governance model built for a traditional SaaS stack wasn't designed for an AI platform where activity takes the form of a conversation.
The AI transformation, governed and secure# #
C1 already governs access to Claude Enterprise and the Claude Platform. When someone joins, they get Claude access. When they leave, they lose it. Developer API keys are governed rather than left to accumulate. Group memberships stay in sync with your identity provider.
That's the identity layer. Today, C1 adds the activity layer.
With the Compliance API integration, C1 doesn't just know who has access to Claude - it knows what they're doing with it. Activity event logs from Claude Enterprise and the Claude Platform sit alongside your identity records in the same platform, informing the same reviews and feeding the same audit trails.
That's the governance model transformation-scale AI requires.
Bring clarity, context, and control to the AI era# #
Run access reviews based on actual usage. C1 can surface which Claude Enterprise users and agents have been active in the last thirty days, and which haven't. Reviews that used to sweep the entire organization can now focus on the access worth scrutinizing.
Trace activity back to identity. When a Claude Platform API key generates unusual volume, C1 knows whose key it is, what role they hold, and what else they have access to. Activity without that context is noise; with it, it's a signal.
Give auditors a complete evidence trail. Regulators don't just ask who had access - they ask what those people did with it. C1 now holds both answers: the access request, the approval, and the activity record that followed, for human users and AI agents.
Close access that outlasts its purpose. Claude Enterprise seats granted for a project that has ended, API access that was never deprovisioned, admin permissions nobody thought to revisit - C1's automated lifecycle workflows flag and remove this access before it becomes a finding.
How the data flows# #
Claude's Compliance API provides programmatic access to activity event data from Anthropic-hosted Claude deployments. C1 receives activity event logs covering user logins, admin actions, and configuration changes.
That data lands in C1 alongside your identity records, not in a separate dashboard you check after something goes wrong.
Governance is what makes the transformation defensible# #
The organizations moving fastest on AI aren't the ones with the fewest controls. They're the ones whose controls don't slow them down. C1's integration with Claude's Compliance API powers this transformation.
With C1 governing both human and non-human identities within Claude, companies can continue to innovate securely. C1 customers can enable the integration in connector settings today.
New to C1? Book a demo to see how we govern access and activity across your full AI stack.