Anthropic Claude Connector

Before You Begin

The Anthropic Claude connector pulls conversations, projects, audit events, per-user activity and usage summaries. The data is read from Anthropic's APIs using an API key.

What you'll need:

• An Anthropic Enterprise plan on Claude.ai (the Compliance API is Enterprise-only)
• The Primary Owner role on your parent Anthropic organization — only Primary Owners can create keys with compliance scopes
• Both the Compliance API and the Analytics API enabled for your organization (see the next section)

Note: Activity Feed events become queryable after a delay of up to 1 minute and are retained for 6 years. Chat, file, and project content follows your organization's own retention policy — indefinite by default.

Note: Anthropic's Analytics API has an inherent 3–4 day data delay, so per-user activity and usage summaries in Section reflect activity from a few days prior.

Enable Both APIs for Your Organization

Keys can only carry a scope once the matching API is switched on, so turn on both before creating anything. This is a one-time action performed by the Primary Owner.

1. Log in to claude.ai as your organization's Primary Owner.
2. Click your profile icon and open Settings.
3. Open the API section for your organization.
4. Toggle Compliance API to On.
5. Toggle Analytics API to On.
6. Confirm each change if prompted.

Important: Turn on both toggles before creating the key. If only one is enabled, the key-creation dialog will not offer the scopes belonging to the other, and a key's scopes cannot be changed after it is created.

Note: If you do not see these options, your account is not the Primary Owner or your plan does not include Compliance API access. Contact your Anthropic representative to confirm Enterprise entitlement.

Create One Key with the Four Required Scopes

With both APIs enabled, Anthropic offers a single Create key dialog listing every available scope together. One key covering all four scopes is all Section needs.

1. Still signed in as the Primary Owner, open the key-creation dialog and click Create key.
2. In the Name field, enter a recognizable label such as Section AI — Claude Connector.
3. Under Scopes, check all four of the following:
   • ✅ read:compliance_activities — the Activity Feed (logins, chat events, project events)
   • ✅ read:compliance_user_data — chat metadata and message content
   • ✅ read:compliance_org_data — organization-level Compliance API access
   • ✅ read:analytics — per-user activity and usage summaries
4. Leave delete:compliance_user_data unchecked — Section never deletes your data and does not need it.
5. Click Create and copy the key immediately; it is shown only once.

Important: Scopes are immutable once the key is created. If you miss one, you must delete the key and create a new one.

Note: Keys are org-owned — they keep working even if the person who created them later leaves the organization.

Add the Key to Section

Section uses this key for both the Compliance and Analytics APIs.

1. Return to the Anthropic Claude API connector in Section.
2. Paste your key into the API Key field.
3. Click Connect.

Section validates the key against both APIs before saving. If a scope is missing, the error names which one, so you can create a replacement key with the full set.

Once connected, the first sync begins automatically and usage data appears in your dashboards within a few minutes.

Important: Treat this key like a password. It grants read access to every chat, file, and audit event in your Anthropic organization. Do not share it over email or chat, and do not commit it to source control.

Note: If the connector reports an error later, use Test Connection on the connector panel to re-check the key. A key revoked in Anthropic will fail here first.

Value to copy: The key from the Anthropic Create key confirmation dialog. Paste it into the API Key field.