> ## 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.

# ChatGPT Enterprise

> Connect ChatGPT Enterprise compliance logs and workspace-linked activity.

Forge polls the ChatGPT Compliance Logs Platform with a workspace-scoped
credential. The connector is a detective source for Enterprise activity; it
does not place Forge inline with the ChatGPT user interface.

## Connection

| Field              | Description                                         |
| ------------------ | --------------------------------------------------- |
| Workspace ID       | ChatGPT Enterprise workspace whose logs Forge reads |
| Organization ID    | Optional OpenAI API Platform organization scope     |
| Compliance API key | Read credential stored as a Forge-managed secret    |

The current collector requests recent `CONVERSATION` log records from:

```text theme={"system"}
/v1/compliance/workspaces/{workspace_id}/logs
```

If an `org-...` identifier is supplied instead, Forge uses the organization
scope exposed by the provider.

## Evidence

Compliance records preserve the native log ID, event type, timestamp, workspace
scope, and provider payload safe for customer review. Workspace-linked users,
GPTs, connectors, and files can become inventory context when those references
are present in the returned logs.

Prompt and response visibility is recorded as `metadata_only` unless the
provider record includes content that Forge is permitted to retain. A log-file
record is not presented as proof that full conversation content was collected.

## Setup

1. Create a ChatGPT Enterprise Compliance Logs API key and copy the workspace
   ID from the Enterprise workspace.
2. Save both values under **Settings → Integrations → ChatGPT Enterprise**.
3. Run **Test setup**, then start a sync.
4. Generate a known low-risk conversation event and verify its native log ID
   appears after the provider's delivery delay.

## Enforcement

This connector remains a detective source and is not itself inline. Supported
ChatGPT browser traffic can be governed separately through agentless Network
routing or Device Agent's transparent proxy. The routing layer decrypts the
selected AI traffic, sends it through the LLM Gateway, and records the resulting
session and policy decisions.

Customer-owned GPT actions, Apps SDK tools, and MCP connections can also use the
MCP Gateway when their protocol and upstream are supported.

## Verification

| Result                  | Meaning                                                                    |
| ----------------------- | -------------------------------------------------------------------------- |
| `401` / `403`           | The Compliance key is invalid or lacks workspace access                    |
| Healthy, no records     | The query succeeded but no matching recent conversation logs were returned |
| Records without content | Provider delivered metadata-only compliance files                          |
| Unresolved actors       | Connect an identity provider and verify email or provider-ID correlation   |

Revoke the Compliance API key to disconnect the source. Network, Device Agent,
LLM Gateway, and MCP Gateway routing are configured and removed separately.