Claude (Anthropic) integration

Comma captures activity from Claude Enterprise and Claude Console by polling Anthropic’s Compliance API. A Compliance Access Key unlocks conversation transcripts too. You configure the connection once from your Comma dashboard. There is no relay service and no per-user sign-in.

This connector is rolling out behind the AI Archiving feature flag. If you do not see the Claude (Anthropic) card under Workspace Integrations, ask the Comma team to enable it for your organization.

Capture coverage

With a Compliance Access Key (Claude Enterprise)

The activity feed and every conversation created or updated within your configured backfill window, including conversations started before you enabled the Compliance API.
The current transcript: user prompts, Claude’s responses, tool calls and results, message timestamps, model and conversation owner. Long tool inputs and results are cut at Anthropic’s limit and marked as truncated. File and artifact references include name, type, size and fingerprint; file bytes are not captured.
A fresh snapshot when a conversation changes. Conversations deleted in Claude are recorded as deleted, with the time of deletion.

With an Admin API key (eligible Claude Console organizations)

Claude Team and individual claude.ai plans have no Compliance API access and cannot connect.

Activity feed events only: chats created or updated, files uploaded, projects changed, sign-ins and settings changes. Comma stores the event type, the Anthropic IDs involved and the timestamp.
No conversation text.

Capture is not real-time. Comma checks every 10 minutes. The first pass over your history can take a while for a large organization. Anthropic starts recording activity when you enable the Compliance API; earlier conversation content is still reachable with a Compliance Access Key, but earlier activity is not.

Not captured yet: the bytes of uploaded and generated files, Claude Projects content, Claude Code and Cowork sessions, and memory. Ask the Comma team if you need one of them.

What you need

One of two keys: a Compliance Access Key from claude.ai (starts with sk-ant-api01-) with both read:compliance_activities and read:compliance_user_data, or an Admin API key from Claude Console (starts with sk-ant-admin01-).
Your Anthropic organization ID, a UUID. Use the parent organization ID for Enterprise. Otherwise, use the organization ID in Console settings.
The Compliance API enabled where you create the key. For Enterprise, the primary owner opens Organization settings > API in claude.ai, enables the Compliance API and creates a Compliance Access Key covering the parent organization with both scopes. Copy it when it appears; the key is shown once. In Claude Console, enable it under Settings > Security & data > Compliance, then create an Admin API key under Settings > Admin keys.
A Comma team admin login and about 10 minutes.

How to enable it

Sign in to the Comma Compliance dashboard.
Open Integrations, then Workspace Integrations, and click Connect on the Claude (Anthropic) card.
Give the connection a name and enter your Anthropic organization ID.
Paste either key into the Compliance Access Key field. Comma stores it encrypted and never shows it again. On edit, leaving this field blank keeps the saved key.
Set the backfill window (days). The default is 90 days. For conversations, raise it to reach further back, or set it to 0 to capture every conversation your organization still holds. Anthropic’s retention settings limit the available history.
Click Test and connect. Comma tests the key before saving and picks the capture level automatically. If the test fails, the form explains the problem and nothing is saved.

The connection page shows which capture level the key unlocked: Activity feed and conversations or Activity feed only.

Which key should I use?

Enterprise owners should use a Compliance Access Key to archive conversations and the activity feed. An eligible Claude Console organization without Enterprise can only create an Admin API key and gets the activity feed, with no conversation text. Claude Team and individual plans are not eligible. You can swap in a Compliance Access Key later on the Edit page without reconnecting; the next poll starts capturing conversations.

Check the connection

The connection page shows Capture level: Activity feed and conversations or Capture level: Activity feed only. For activity feed only, a note explains that transcripts need a Compliance Access Key from a Claude Enterprise organization.

The connected message matches the capture level:

Connected. We check for new and updated conversations every 10 minutes
Connected. We check the activity feed every 10 minutes

If Anthropic rejects the key, the connection shows Needs attention with a sentence explaining the problem. Open Edit Claude connection, paste a replacement key and click Test and update. Syncing resumes once the new key passes the test.

Connecting more than one organization

A team can connect more than one Anthropic organization, but only one connection per organization ID. The organization ID cannot be changed after creation. To use a different organization, remove the connection and add a new one.

Pause or remove the connection

Disable syncing stops future capture. Resume syncing turns it back on.
Remove Claude connection stops future capture and deletes the stored access key.

Records already archived are retained in both cases.

Claude vs. Arc Relay

This connector captures Claude Enterprise conversations from the Anthropic Compliance API. To capture agentic AI activity across providers, such as tool calls made by your own agents, use Arc Relay. The two are complementary.

ChatGPT (OpenAI) integration, the matching connector for ChatGPT Enterprise
Arc Relay - AI Agent Archiving
Anthropic’s own Compliance API documentation