OpenAI ChatGPT setup - Configview Support

ConfigView inventories your ChatGPT Enterprise workspace — seats, custom GPTs, projects, stored memories, and the compliance event logs — through the Compliance API. You will end up with 2 secrets in ConfigView (OPENAI_CHATGPT_COMPLIANCE_KEY, OPENAI_CHATGPT_WORKSPACE_ID) when setup is complete.

This is not the same as the OpenAI developer API. OpenAI splits into two products with two separate consoles and two key types. This page covers ChatGPT Enterprise seats and workspace activity. If you want API spend and token usage, that is the OpenAI Platform integration and a different credential entirely. Most organizations that use both will want both apps enabled.

Requires ChatGPT Enterprise. The Compliance API is an Enterprise feature. It is not available on Team, Plus or Free, and there is no partial version of this integration on those plans.

Step 1: Create the Compliance API key

Sign in to your ChatGPT Enterprise workspace as a workspace Owner
Open Settings → Compliance (or Compliance API, depending on your workspace version)
Generate a Compliance API key and name it ConfigView
Copy the key — it is shown once
Note your Workspace ID from the same screen

If you do not see a Compliance section, the feature has not been enabled for your workspace. Your OpenAI account contact can turn it on — it is not something a workspace admin can self-serve on every plan.

Step 2: Add the secrets to ConfigView

Go to your ConfigView dashboard: https://{companyname}.configview.com/admin/secret/
Add both secrets:

Secret name	Value
`OPENAI_CHATGPT_COMPLIANCE_KEY`	The Compliance API key from Step 1
`OPENAI_CHATGPT_WORKSPACE_ID`	The workspace ID from Step 1

Click Save for each

Step 3: Enable the ChatGPT scripts in ConfigView

Go to: https://{companyname}.configview.com/admin/cron/
You should see OpenAI ChatGPT in the list of available apps
Select the scripts you want to run:

Inventory

Script	Notes
Workspace	The workspace itself — plan, verified domains, seat count, active user count. Cheap; enable it.
Users	Every member — role, status, licence type, last active and last login.
Custom GPTs	GPTs built in the workspace, with owner and visibility.
Projects	Workspace projects, with owner and archive state.
Stored Memories	Per-user stored memories. See the privacy note below before enabling.

Compliance logs All four read the same /logs endpoint and differ only by event type.

Script	Event type	Notes
Conversations Log	`CONVERSATION_LOG`	Conversation metadata — title, message count, model, which GPT or project.
Admin Audit Log	`ADMIN_AUDIT_LOG`	Administrative changes — who did what to whom.
User Authentication Log	`AUTH_LOG`	Sign-in events, outcome, SSO provider, IP and user agent.
Codex Usage Log	`CODEX_USAGE_LOG`	Codex sessions with model and token counts.

Click Save

Step 4: Verify

Go to: https://{companyname}.configview.com/admin/cron/
Run the OpenAI ChatGPT health check

If a check fails:

401 / 403 — The key is wrong or the Compliance API is not enabled for the workspace. See the note in Step 1.
404 — OPENAI_CHATGPT_WORKSPACE_ID is wrong. Every request is scoped to that ID, so a typo fails everything uniformly rather than just one script.
Logs return nothing but inventory works — Compliance logs are time-windowed and only cover the retention period your plan provides. A quiet workspace, or a first run outside the window, legitimately returns zero rows.

Data Tables

Once the scripts run, the corresponding tables are created in your database. All tables include a run_at column for historical tracking. Every request is scoped to /v1/compliance/workspaces/{workspace_id}/....

Table	Source	Key Columns
`chatgpt_workspace`	“ (workspace root)	workspace_id, name, plan, domains, seat_count, active_user_count
`chatgpt_users`	`users`	user_id, email, name, role, status, license_type, created_at, last_active_at, last_login_at, sso_external_id
`chatgpt_gpts`	`gpts`	gpt_id, name, description, owner_user_id, owner_email, visibility, created_at, updated_at
`chatgpt_projects`	`projects`	project_id, name, owner_user_id, owner_email, created_at, updated_at, archived_at
`chatgpt_memories`	`memories`	memory_id, user_id, user_email, content_length, content_preview, created_at, updated_at
`chatgpt_conversations`	`logs` (`CONVERSATION_LOG`)	conversation_id, user_id, user_email, title, message_count, model, gpt_id, project_id, created_at, updated_at
`chatgpt_admin_audit`	`logs` (`ADMIN_AUDIT_LOG`)	event_id, event_type, event_time, actor_id, actor_email, target_type, target_id, ip_address
`chatgpt_user_auth`	`logs` (`AUTH_LOG`)	event_id, event_time, user_id, user_email, ip_address, user_agent, outcome, sso_provider
`chatgpt_codex_usage`	`logs` (`CODEX_USAGE_LOG`)	event_id, event_time, user_id, user_email, session_id, model, input_tokens, output_tokens, tool_calls

Things worth knowing

Conversations are metadata, not content. chatgpt_conversations records the title, message count, model and owner — not the messages. That is deliberate: it answers adoption and attribution questions without putting conversation bodies in your database. Stored Memories is the one to think about before enabling. chatgpt_memories stores content_preview and content_length — a preview is still user-entered content, and it will sit in your database and appear in query results. Decide whether that is acceptable under your own data-handling policy before turning the script on. Everything else in this integration is metadata. last_active_at and last_login_at are different, and the gap matters. Login is an authentication event; active is actual use. A seat with recent logins but no activity is the clearest candidate for reclamation, and you need both columns to spot it. The four log scripts share one endpoint and one rate budget. They all read /logs with a different event_type. Enabling all four multiplies the calls against the same limit, so if you are only after seat reclamation, Conversations and Auth are usually enough. Seat counts have two sources. chatgpt_workspace.seat_count is what OpenAI reports for the workspace; counting rows in chatgpt_users is what the API enumerates. If they disagree, trust the workspace figure for billing questions and investigate the difference — pending invites and recently removed members are the usual explanation.

​Step 1: Create the Compliance API key

​Step 2: Add the secrets to ConfigView

​Step 3: Enable the ChatGPT scripts in ConfigView

​Step 4: Verify

​Data Tables

​Things worth knowing