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

# Claude Enterprise

> Connect Anthropic Admin and Claude Enterprise Compliance APIs.

Claude Enterprise uses two provider APIs with different coverage. The
Anthropic Admin API supplies organization inventory. The Claude Compliance API
supplies Enterprise activity evidence and, when explicitly authorized,
provider remediation operations.

## Credentials

| Credential             | Coverage                                                               |
| ---------------------- | ---------------------------------------------------------------------- |
| Admin API key          | Users, workspaces, invites, API keys, roles, and organization metadata |
| Compliance API key     | Authentication, chat, file, project, admin, and platform activity      |
| Parent organization ID | Optional organization scope for Admin and Compliance reads             |

Forge stores API keys as managed secrets and reports the two capability lanes
independently.

## Provider reads

The base Admin collector queries:

```text theme={"system"}
/v1/organizations/users
/v1/organizations/workspaces
/v1/organizations/invites
/v1/organizations/api_keys
```

When a Compliance key is configured, Forge also polls:

```text theme={"system"}
/v1/compliance/activities
```

Activity receipts retain the provider event type, timestamp, actor and
workspace references, affected object, and content-visibility state.

## Setup

1. Create an Anthropic Admin API key with organization, user, workspace,
   invite, and API-key read access.
2. Create a separate Claude Enterprise Compliance API key if activity coverage
   is required.
3. Save the keys and optional parent organization ID under
   **Settings → Integrations → Claude Enterprise**.
4. Test the connection and verify Admin and Compliance lanes separately.
5. Run a sync and compare returned users, workspaces, and a known activity
   event with the Anthropic console.

## Remediation

Read-only setup does not delete provider objects. Remote deletion of chats,
files, projects, documents, generated files, or artifacts requires the
corresponding Compliance delete scope and an explicit Forge action. Do not add
those scopes for inventory-only deployments.

Claude UI conversations are not inline-governed by this connector. Supported
Claude browser and desktop traffic can be governed separately through
agentless Network routing or Device Agent's transparent proxy. Forge reroutes
selected traffic through the LLM Gateway and direct MCP connections through the
MCP Gateway.

## Verification

| Symptom                         | Check                                                  |
| ------------------------------- | ------------------------------------------------------ |
| Admin works, activity does not  | Enterprise entitlement and Compliance API key          |
| Users appear, workspaces do not | Admin key scope and parent organization                |
| Activity lacks content          | Provider event type and Compliance content entitlement |
| Remediation is unavailable      | Explicit delete scope for that object type             |

Offboarding requires revoking both keys and removing any separately configured
network, endpoint, LLM Gateway, or MCP Gateway route.