> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Anthropic

> Connect Anthropic to gain visibility into Claude usage, analytics, and compliance activity

Glow's Anthropic integration collects usage, analytics, and compliance data across the Anthropic platform. It is a single connection authenticated with **one API key** that carries both the analytics and compliance scopes.

| Data                      | What it collects                                                                                 |
| ------------------------- | ------------------------------------------------------------------------------------------------ |
| **Analytics**             | Per-user Claude usage, daily org-level activity summaries, custom skills, installed connectors   |
| **Compliance activities** | Audit trail of activity-feed events (auth, chat, file, project, admin, and platform actions)     |
| **Remote settings**       | The current Claude Code managed-settings bundle, reconstructed from the compliance activity feed |

## Prerequisites

<Check>A Claude Enterprise plan with **Primary Owner** access to claude.ai</Check>
<Check>The Compliance API enabled for your organization by Anthropic (required for the compliance scopes)</Check>

The API key must carry all of the following scopes:

* `read:analytics`
* `read:compliance_activities`
* `read:compliance_org_data`
* `read:compliance_org_settings`
* `read:compliance_user_data`

## Setup Instructions

### Create the API Key

<Steps>
  <Step title="Confirm Compliance API eligibility">
    The compliance scopes require the Compliance API to be enabled for your organization by Anthropic. Contact your Anthropic account team to enable it before minting the key.

    <Note>
      Anthropic enables the Compliance API for Enterprise organizations that use a **parent organization** — an umbrella organization that contains one or more sub-organizations, used by larger enterprises to segment teams or departments. This is a property of how your organization is set up in Anthropic, not a Glow setting. If the Compliance API is not enabled, the key cannot be issued the compliance scopes and the connection fails (see Troubleshooting).
    </Note>
  </Step>

  <Step title="Open Claude admin settings">
    Log in to [claude.ai](https://claude.ai) as the **Primary Owner** of your Enterprise organization. Only Primary Owners can mint API keys.
  </Step>

  <Step title="Create the key with all required scopes">
    Create a new API key with a descriptive name (e.g., "Glow Integration") and grant it all five scopes listed in [Prerequisites](#prerequisites).
  </Step>

  <Step title="Copy the key">
    Copy and securely store the key value. It is displayed only once.
  </Step>
</Steps>

### Complete the Integration

<Steps>
  <Step title="Provide the credential">
    Provide the API key to your Glow representative or enter it in the Glow console.
  </Step>

  <Step title="Connect in the Glow console">
    In the Glow console, open **Integrations → Anthropic** and enter the API key in the connection drawer.
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The connection fails with 'requires an organization that belongs to a parent organization'">
    This error comes from Anthropic when the Compliance API is not enabled for your organization. Anthropic enables it for Enterprise organizations set up under a parent organization (an umbrella org containing sub-organizations). Contact your Anthropic account team to enable the Compliance API, then re-issue the key with the compliance scopes.
  </Accordion>

  <Accordion title="The connection fails with an HTTP 403 / scope error">
    The API key is missing one or more required scopes. Confirm the key carries all five scopes listed in [Prerequisites](#prerequisites): `read:analytics`, `read:compliance_activities`, `read:compliance_org_data`, `read:compliance_org_settings`, and `read:compliance_user_data`. Re-mint the key with the missing scopes if needed.
  </Accordion>

  <Accordion title="Why is recent analytics data missing?">
    The analytics engagement endpoints only expose a day once it has settled, so the most recent days are not yet available. Glow fetches up to the latest settled day and re-fetches a lookback window each run to recover any missed days.
  </Accordion>
</AccordionGroup>