> 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-console.md).

# Claude Console

Connect Sola and Claude Console to get security insights

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

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

With the Claude Console integration, you can:

* Gain visibility into user access, roles, and workspace permissions across your Anthropic organization.
* Monitor API key status, creator, and workspace assignment to identify stale or unmanaged keys.
* Track organization invitations, including pending, accepted, and expired, to maintain access governance.
* Monitor token usage and Claude Code activity by model, workspace, and user.

{% 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 Console 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 Console***.

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

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

### Connect Claude Console to Sola

To connect Claude Console, you'll need an Anthropic Console account with an Admin role.

{% tabs %}
{% tab title="Admin API Key" %}
This method uses an Admin API Key to securely grant Sola read-only access to your Anthropic organization data.
{% endtab %}
{% endtabs %}

## Explore Claude Console templates

![](https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FXMRpFbpx9LSRblEJ68Mo%2FApp-Gallery-icon.svg?alt=media\&token=a7a5e8e8-f1fc-4dab-b430-5e5c0ad78e66) Get started with [Claude-focused security templates](https://sola.security/templates/?search=claude), built by our expert security team.

<figure><img src="https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2Fh8LtsLpoC4ctsyKoRCq1%2FAnthropic_banner.svg?alt=media&amp;token=b1e99f59-2fca-4be7-9634-04bc3656edd9" alt="Anthropic"><figcaption></figcaption></figure>

***

## 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
