> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/integrations/data-sources/claude-enterprise.md).

# Claude Enterprise

## Overview <a href="#overview" id="overview"></a>

The Claude Enterprise integration connects data from your Claude Enterprise account to your Sola workspace, making it easy to search and find answers to your specific use cases.

With the Claude Enterprise integration, you can:

* Monitor user and admin activity across your Claude Enterprise organization, including authentication events, chat interactions, file uploads, and administrative actions.
* Track organizational users, groups, and custom RBAC roles to support access governance and compliance requirements.
* Gain full visibility into projects, including creator, privacy settings, and attached files across your Claude Enterprise organization.
* Monitor chat conversations to support eDiscovery and data loss prevention investigations.

{% hint style="warning" %}
**Your data can only be retrieved, never modified.**

Once connected, your data is securely stored, and access is restricted to retrieving configurations and metadata only. Authentication methods ensure secure delegation of permissions while maintaining data integrity.
{% endhint %}

## Set up Claude Enterprise data source integration with Sola <a href="#set-up-wiz-data-source-integration-with-sola" id="set-up-wiz-data-source-integration-with-sola"></a>

{% columns %}
{% column width="66.66666666666666%" %}
Go to ***Integrations*** > [***Data Sources***](https://app.sola.security/integrations/data-sources) > click ***New data source*** > select ***Claude Enterprise***.

*The Sola wizard will take you through the steps.*
{% endcolumn %}

{% column width="33.33333333333334%" %} <a href="https://app.sola.security/integrations/data-sources?integration=anthropiccompliance" class="button primary">Set up Claude Enterprise -></a>
{% endcolumn %}
{% endcolumns %}

To connect Claude Enterprise, you'll need to be the Primary Owner of your Claude.ai parent organization, with the Compliance API enabled for your organization.

{% tabs %}
{% tab title="Compliance API Key" %}
This method uses a Compliance Access Key generated from Claude.ai to grant Sola read-only access to your Claude Enterprise compliance data.
{% endtab %}
{% endtabs %}

***

## FAQs

### What is the difference between the Claude data sources?

Sola offers three Anthropic integrations:

* [Claude Console](/integrations/data-sources/claude-console.md): for API platform customers (Build, Scale, or Team).
* [Claude Enterprise](/integrations/data-sources/claude-enterprise.md): for seat-based claude.ai plans, with compliance and activity data for eDiscovery and DLP.
* [Claude Enterprise Analytics](/integrations/data-sources/claude-enterprise-analytics.md): for seat-based claude.ai plans, with usage, adoption, and cost analytics.
* [Claude Code](/integrations/data-sources/claude-code.md): for organizations using Claude Code as an AI coding agent, with visibility into developer sessions, tool calls, and prompts.

Use Console if you connect to Anthropic through the API platform. If you're on a seat-based claude.ai plan, use the Claude Enterprise integrations; you can connect both.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sola.security/integrations/data-sources/claude-enterprise.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.