Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To connect KnowBe4 Agent Risk Manager to Claude’s Compliance API, have the Anthropic organization’s Primary Owner create a compliance API key with both read:compliance_org_data and read:compliance_user_data. Add that key in Agent Risk Manager under Setup > Integrations, choose whether to discover organizations automatically or specify IDs, then select Save & Connect. The integration tests the connection before saving. After it reports Healthy, review collected activity at Discovery > AI Activity Log.

Check access and eligibility before setup

  • You need administrative access to the KnowBe4 Security Awareness Training console and Agent Risk Manager.
  • Your organization needs an Anthropic subscription and access to create API keys. In the documented setup flow, only the Anthropic organization’s Primary Owner can create the compliance key. If you are not the Primary Owner, ask that person to create it.
  • Agent Risk Manager is described as being in technical preview in KnowBe4’s quickstart dated October 2, 2026. KnowBe4’s September 29 announcement says the Claude integration is available to select customers in early access, while Anthropic’s integration directory lists general availability as planned for November 2026. These are distinct vendor rollout descriptions, not confirmation that every organization is eligible; check with KnowBe4 and Anthropic for your account’s availability. KnowBe4 quickstart, KnowBe4 announcement, Anthropic integration information.

The setup guide does not state a price or establish that all organizations can enable the integration. Confirm commercial availability with the vendors.

Create the Claude Compliance API key

  1. Sign in to the Claude console as your organization’s Primary Owner.
  2. Open the profile menu, select Organization settings, then API.
  3. Select + Create key and grant both required scopes: read:compliance_org_data and read:compliance_user_data. The organization-data scope supports automatic organization-ID discovery; the user-data scope permits access to user chats, messages, and files, as described in KnowBe4’s setup guide.
  4. Create the key and copy its value to a secure location. The guide warns that the key cannot be accessed again in that creation flow. KnowBe4 later displays whether a key is configured, not the key value.

See the KnowBe4 Claude Compliance Integration Guide for the documented key requirements.

Add the integration in Agent Risk Manager

  1. Sign in to the KnowBe4 Security Awareness Training console.
  2. Open the grid menu and select Agent Risk Manager.
  3. In the Agent Risk Manager sidebar, go to Setup > Integrations.
  4. Under Add a New Integration, select Anthropic Claude Compliance.
  5. Enter the compliance API key. Leave Organization IDs blank for automatic discovery, or enter a comma-separated list of Anthropic organization IDs to limit collection to those organizations.
  6. Select Save & Connect. Agent Risk Manager tests the connection before saving.

Check connection status and troubleshoot errors

Find the saved connection at Setup > Integrations. Statuses can include Healthy, Error, Paused, Pending, and Setting Up. Healthy indicates the connection is working. For another status, open the integration and inspect its setup or error details.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Missing required scopes: Create a new compliance key with both required scopes. The setup guide does not describe adding scopes to the existing key as a remedy.
  • Organization IDs are no longer accessible: Remove the inaccessible IDs, or clear the field to allow automatic discovery.
  • An Anthropic Claude Compliance integration already exists: Open and inspect the existing integration rather than creating a duplicate.
  • Pending: Complete any remaining setup steps.
  • Setting Up: Wait a few minutes, then refresh the page.
  • Error: Review the configuration and rerun the connection test.

The state-specific guidance is in KnowBe4’s Agent Risk Manager Quickstart Guide.

Find collected activity and understand what the integration does

  • Discovery > AI Activity Log: View collected Claude activity after the connection becomes Healthy.
  • Users > User Activity: View each user’s Acceptable Use Policy acknowledgment status and browser-extension health.
  • Dashboard: Review vendor data.
  • Policies > Data Detection Policies: Investigate detections.

Anthropic describes the KnowBe4 integration as using the Compliance API to inventory AI agents and Claude usage, associate activity with a human, system, or agent source, and detect risks such as prompt injection, sensitive information disclosure, excessive agency, and unbounded consumption. KnowBe4 also describes activity visibility and risk analysis. These are vendor-stated capabilities, not independent test findings. See Anthropic’s integration information and KnowBe4’s announcement.

The Compliance API integration is for ingesting and monitoring activity; KnowBe4 says integration policies, including blocking unwanted activity, are coming soon. The browser extension is a separate mechanism: the quickstart describes its policies as a way to control access to AI vendors. Do not treat connecting the Compliance API as enabling a block on Claude interactions. For product context, see KnowBe4’s quickstart and Agent Risk Manager product page.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Pause, resume, change, or remove the connection

Open the Claude connection under Setup > Integrations to pause or resume collection, change the API key, or delete the integration. Pausing stops collection, and data missed during the pause cannot be backfilled after resuming. Deleting stops monitoring and cannot be undone. These effects are documented in the KnowBe4 setup guide.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.