Connect Claude Compliance to Rig

    Sync the Claude Enterprise audit log, organisations, users, roles, groups, projects and spend limits into Rig, so you can query who did what in Claude. Chats and their full messages can be added too, but they are off unless you tick them. This connector uses a Compliance Access Key.

    Before you start

    • You need a Claude Enterprise organisation with the Compliance API enabled. The primary owner enables it at claude.ai, under Organization settings then API.
    • The primary owner creates the key. An organisation owner can create one that covers only their own organisation.
    • This is not the Analytics API key or an Admin API key. An Admin API key reaches the Activity Feed only.

    Step 1: Create a Compliance Access Key

    1. Sign in to claude.ai as the primary owner, and check that the Compliance API is enabled.
    2. Go to Organization settings then API and find the Keys section.
    3. Click Create key, name it, and pick the scopes read:compliance_activities, read:compliance_org_data and read:compliance_user_data. Add read:spend_limits if you want spend limits.
    4. Click Create, then copy the key, which starts with sk-ant-api01-. Anthropic shows it once.

    Scopes cannot be changed later
    Scopes are fixed when the key is created. To change them, create a new key and delete the old one. Do not tick delete:compliance_user_data, because Rig only reads.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Claude Compliance, open the card and click Connect.
    3. Compliance Access Key: the key from Step 1.
    4. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    5. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Claude Compliance lands in its own anthropic_compliance schema in your warehouse:

    • Activities: the audit log of events in one table, with the actor's name and email address, IP address and event details. It holds no prompt or response text.
    • Organisations and projects: organisation metadata and projects.
    • People: users with their emails, roles, groups and group members.
    • Spend limits: members' spend limits and limit increase requests. Needs the spend limits scope.
    • Chats and chat messages: chat titles and creators, and the full text of conversations. Off by default.

    Chats and chat messages hold employees' conversations. They are only pulled if you tick them when you choose streams.

    Good to know

    • A stream whose scope the key lacks is shown as unavailable when you connect, so you can add the scope with a new key.
    • Activities can arrive a few minutes late, so each sync starts 5 minutes before the last one finished and merges on the event ID.
    • A chat that is hard-deleted in Claude stays in your warehouse until you remove it there.
    • To disconnect Claude Compliance, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Audit activity in Claude
    • Review users, roles and groups
    • Follow spend limits

    More ideas for using Claude Compliance

    Was this guide helpful?