Claude Integration Guide
Claude Enterprise v2026.03.21
Versioning
API Version: v2026.03.21
Document updated: 2026-04-23
Overview
This guide provides step-by-step instructions for IT administrators to integrate Opsin with your Claude Enterprise organization. The integration enables Opsin to monitor your Claude Enterprise environment for security and compliance purposes.
Note on frequent UI changes: Claude Enterprise settings pages and labels change regularly. This guide is written to be resilient: it lists the most common navigation paths, plus what to look for on the page if the labels differ.
Prerequisites
Before you begin, ensure you have:
- Claude Enterprise organization (not a test/trial workspace)
- Compliance API enabled for your organization (see below)
- Access level: You must be able to create Compliance access keys. In most orgs this is limited to Primary Owner(s).
Who can complete this setup?
In many Claude Enterprise orgs today, only a Primary Owner can view and create Compliance access keys. If your organization has a single Primary Owner, this becomes a single point of dependency.
Recommended:
- Maintain 2+ Primary Owners (or an equivalent break-glass approach) to avoid operational risk.
- Use a dedicated admin identity (e.g., an IT-admin account) as a Primary Owner where appropriate.
- Store the generated key in your enterprise secrets manager and rotate on a regular cadence.
If you don't see a "Compliance access keys" section, it typically means either:
- You're not a Primary Owner, or
- Compliance API access is not enabled for your org.
In that case, a Primary Owner should contact your Anthropic representative to request Compliance API access / enablement.
What Information Opsin Needs
To successfully integrate Opsin with your Claude Enterprise workspace, you'll need to provide Opsin with:
- Claude Organization ID
- Compliance Access Key
Integration Steps
Step 1: Find your organization ID
- Navigate to Organization Settings: https://claude.ai/admin-settings/organization.
- Scroll to the bottom to find the Claude Organization ID.
If the URL or label changes: Look for a page under Admin or Organization settings that lists organization metadata and an explicit "Organization ID".
Step 2: Confirm Compliance API is enabled
If you cannot find Compliance key management in Settings, your org may not have Compliance API enabled.
- Confirm you are signed in as a Primary Owner.
- If still missing, contact your Anthropic representative to request access.
Up-to-date vendor documentation: https://support.claude.com/en/articles/13015708-access-the-compliance-api
Step 3: Generate a Compliance Access Key
- Go to Data Management Settings: https://claude.ai/settings/data-management
- Find the section labeled "Compliance access keys" (or similar)
- Click "Create key", give it a name (e.g., "Opsin Security API Key"), and select the following scopes:
- read:compliance_activities : Needed to read activities such as tool calls.
- read:compliance_user_data : Needed to list all workspace users. Without this scope, no messages could be monitored.
- read:compliance_org_data : Needed for collecting the organizations’ information. Without this scope, no messages could be monitored and no Projects analyzed.
- Copy and store the key securely (it is shown only once) — it looks like sk-ant-api01-....
Key handling best practices
- Store in an enterprise secrets manager (1Password/Bitwarden/AWS Secrets Manager/etc.).
- Restrict access to the secret to the smallest admin group.
- Rotate the key periodically and immediately after any suspected exposure.
- Prefer generating a key specifically for Opsin (do not reuse a key used elsewhere).
Step 4: Add the API Key in Opsin
- Visit https://app.opsinsecurity.com/integrations/integrations
- Choose the Claude Enterprise integration
- Enter your Organization ID and Compliance Access Key
Troubleshooting
I can’t see "Compliance access keys": Confirm you are a Primary Owner; otherwise the section may be hidden. If you are a Primary Owner and it’s still missing, Compliance API may not be enabled.
The settings URL 404s or moved: Use the Claude admin/settings sidebar to navigate to Data Management; then search within settings for "Compliance" or "access keys".
We only have one Primary Owner: Add a second Primary Owner (recommended) or create a break-glass Primary Owner identity. Record the process in your internal access review / onboarding runbook.
