Skip to main content
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

The current collector requests recent CONVERSATION log records from:
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

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