Skip to main content
Telara

Integrations / ChatGPT Enterprise

ChatGPT Enterprise logo

ChatGPT Enterprise

ChatGPT Enterprise / Edu — OpenAI Compliance Logs Platform (Audit + Auth + Codex + Conversation logs) for per-user prompt counts, tool usage, GPT invocations, and SSO-anchored governance. Spend-only connector for the AI Platform Spend Governance feature.

API key
Spend

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions NoReal-time events No

Before you connect

Prerequisites

A ChatGPT Enterprise or Edu workspace (not Team, not a personal Plus account).
Workspace owner. Only owners can open the Compliance Platform.

Vendor setup

Get the credential

1
Open the Compliance Platform
Sign in at chatgpt.com as a workspace owner. Open the workspace admin menu → Compliance (Compliance Platform). This is not Settings → API keys and not platform.openai.com.
2
Create a compliance key
In Compliance, create an API key. Copy it immediately. Project keys from platform.openai.com are the wrong class and will be rejected.
3
Paste in Telara
Settings → Integrations → ChatGPT Enterprise. Paste the key. Enter the workspace id if the form asks.

In Telara

Connect in Telara

API key

OpenAI Enterprise Compliance API Key. Provisioned by an Enterprise/Edu workspace owner from the Compliance Platform admin surface. Verified auth shape from the OpenAI Cookbook quickstart: https://developers.openai.com/cookbook/examples/chatgpt/compliance_api/logs_platform ("Authorization: Bearer ${COMPLIANCE_API_KEY}"). The workspace_id is required because every endpoint is scoped to a workspace principal: /v1/compliance/workspaces/{WORKSPACE_ID}/logs. Org-scoped variant (/v1/compliance/organizations/{ORG_ID}/logs) also exists for tenants managing multiple workspaces — model that as a second credential.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key
  • Workspace Id

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by email.

Vendor history: 30 days of vendor-side history.

  • messages_sent
    count
  • prompts_per_user
    count
  • tool_usage_counts
    count
  • gpt_invocations
    count
  • file_uploads
    count
  • sso_logins
    count

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Team, Plus, and API project keys cannot read enterprise compliance exports.
This is not the OpenAI Admin connector and not OpenAI SDK telemetry.