What you get

If your engineers use Claude at work, this connection lets the platform show whether adoption is growing, active users, message volume over time, that sort of thing. It is the same category as Cursor in the AI tools section of your tech stack.

We only pull aggregate stats from Anthropic’s admin APIs. Prompts, chat content, and code from individual sessions never leave Claude’s side in a way we store or display.

Before you start

You need admin access to your Claude organization and an API key that matches your plan:

• Claude Team: use a Team admin API key.
• Claude Enterprise: use the analytics / insights token your admin console provides (the platform labels this as the Enterprise path during setup).

If you are not an org admin, ask whoever manages Claude billing to create the key and hand it to you securely, same as you would for any other admin integration.

Connect Claude

1. Open Settings → Integrations (or the Integrations step during onboarding if you have not finished setup).
2. Make sure Claude is selected under AI tools in your tech stack. If it is not, add it there first and save.
3. Click Connect on the Claude card.
4. Choose Team or Enterprise to match your Anthropic plan.
5. Paste the API key and run Test connection.
6. Save when the test passes.

The first sync usually lands within a few hours. After that, usage refreshes on the platform’s normal schedule. You do not need to reconnect unless you rotate the key.

Rotating or replacing a key

Keys expire or get rotated like any other secret. When that happens:

1. Generate a new key in the Claude admin console.
2. Go back to Settings → Integrations → Claude.
3. Paste the new key, test, and save.

Existing charts keep their history; only new data depends on the updated credential.

Disconnect

Removing Claude from Settings → Integrations stops future syncs. Numbers already in your workspace stay until you clear them manually or replace the connection later.

When something fails

Test connection fails: Double-check the plan toggle (Team vs Enterprise) matches what Anthropic issued the key for. A Team key will not work on the Enterprise path and vice versa.

No usage after a day: Confirm the key still exists in Claude admin and has not been revoked. If it looks fine on Anthropic’s side, give it one more sync cycle; weekly refresh is normal for some metrics.

Wrong org: The key is scoped to the Claude organization it was created in. If your company has more than one Claude org, make sure you are using the one your engineering teams actually use.