Claude Compliance API Connector

Before You Begin

The Anthropic Compliance connector pulls Claude conversations, projects, and audit events from Anthropic's Compliance API into Section. This data powers adoption and engagement analytics. Setup requires an Anthropic Enterprise plan and access to your organization's Primary Owner account. Anthropic lets only Primary Owners create Compliance access keys at the parent-org level.

What you'll need:

  • An Anthropic Enterprise plan on Claude.ai (Compliance API is Enterprise-only)
  • The Primary Owner role on your parent Anthropic organization (only Primary Owners can create Compliance access keys)
  • Enable the Compliance API manually for your organization before you create access keys (see Step 2)

Note: You can query Activity Feed events after a short delay of up to 1 minute. Anthropic retains Activity Feed data for 6 years. Chat, file, and project content follows your organization's retention policies (indefinite by default).

Enable the Compliance API for Your Organization

Before you create Compliance access keys, turn on the Compliance API at the organization level. The Primary Owner performs this one-time action inside Claude.ai settings.

  1. Log in to claude.ai as your organization's Primary Owner.
  2. Click your profile icon and open Settings.
  3. In the left sidebar, select Data and Privacy.
  4. Locate the Compliance API section and toggle it On.
  5. Confirm the change if prompted.

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

Note: If you are setting this up for Claude Console or the Claude API (not Claude.ai), have an organization admin email your Anthropic representative to request activation, then proceed to Step 3.

Create a Compliance Access Key with Required Scopes

Compliance access keys are separate from standard Anthropic API keys. They provide scoped access to compliance data across all linked organizations. Section needs a key with both Activity Feed and user-data scopes so the connector can pull chat metadata, message content, and audit events.

  1. Still logged in as the Primary Owner, go to Settings → Data Management → Compliance access keys.
  2. Click Create key.
  3. In the Name field, enter a recognizable label such as Section AI — Compliance Connector.
  4. Under Scopes, select both of the following checkboxes:
    • read:compliance_activities — required to pull the Activity Feed (logins, chat events, project events)
    • read:compliance_user_data — required to pull chat metadata and message content
  5. Leave delete:compliance_user_data and read:compliance_org_data unchecked — Section does not need them.
  6. Click Create to generate the key.

Important: Scopes are immutable after you create the key. If you forget to enable a required scope, you will need to delete this key and create a new one.

Note: If the Compliance access keys section is missing, either you have not enabled the Compliance API for your organization (revisit Step 2), or you are not signed in as the Primary Owner.

Copy and Save the Compliance API Key

This step captures the secret access key and connects it to Section. Claude.ai shows the key only once. If you navigate away before copying it, create a new key.

  1. After clicking Create in Step 3, Claude.ai displays the new secret access key in a modal.
  2. Click the Copy button next to the key to copy the full value to your clipboard.
  3. Paste it temporarily into a secure password manager or secrets vault before proceeding.
  4. Return to Section and paste the key into the Compliance API Key field.
  5. Click Save to complete the connection.

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: To rotate the key, return to Settings → Data Management → Compliance access keys. Disable or delete the existing key, create a new one with the same scopes, and update the value in Section.

Value to copy: Copy the secret Compliance access key from the Create key confirmation modal in Claude.ai. Paste it into the Compliance API Key field.