Skip to main content

​
Overview

nOps uses a workspace Admin key created in the Global Admin Console to bring ChatGPT Business and Enterprise usage and credit spend into Inform. This is the surface where Codex usage lands when developers run Codex on a ChatGPT plan (seats and AI credits) rather than an API key. Credentials are stored securely and are not shown again after you connect.
This integration is for ChatGPT Business/Enterprise workspaces only. If your organization uses OpenAI Platform (programmatic API usage on platform.openai.com), see OpenAI (Platform) instead — the two credential types are not interchangeable. An Admin key cannot be used for model inference, and a Platform Admin API key is rejected by the workspace endpoints.

​
Prerequisites

  • A ChatGPT Business or Enterprise/Edu workspace eligible for Admin keys
  • A workspace admin or owner who can create Admin keys
  • nOps organization administrator access
Only admins and owners can connect, re-validate, or disconnect. Members see Admin Only on connectable cards.

​
Create an Admin key

  1. Sign in to the Global Admin Console for your workspace.
  2. Open Credentials → Admin keys.
  3. Create a new Admin key and give it a descriptive name (for example nOps Integration).
  4. Set permissions:
    • Owners can choose All, Read only, or Restricted — choose Read only, or Restricted with read access to the cost and analytics categories.
    • Admins are always Restricted — grant read on the cost and analytics endpoint categories.
  5. Copy the key immediately and store it securely.
One Admin key covers one workspace. Connect the integration once per workspace, using a distinct Admin key name for each.
Do not share the Admin key or commit it to source control. If it is lost or compromised, create a new key and connect again in nOps.

​
Codex analytics (optional)

The workspace Admin key covers cost and analytics data. The Codex Analytics API is the one exception: it authenticates with a Platform organization API key whose organization matches the one behind your workspace. If you want Codex analytics alongside credit spend, also create a Platform organization API key at platform.openai.com and paste it into the optional Codex analytics key field. Leave the field empty to ingest cost and usage only.

​
Connect in nOps

​
Where to open ChatGPT (Business/Enterprise)

  • To connect for the first time — go to Settings → Integrations and click the ChatGPT (Business/Enterprise) card.
  • To manage an existing connection — go to Settings → Account Status → Connected apps and click the ChatGPT (Business/Enterprise) chip to re-validate or disconnect.

​
Connect steps

  1. Click the ChatGPT (Business/Enterprise) card or chip.
  2. Enter a Key name and paste the Admin key.
  3. Enter the Workspace ID the key was created in.
  4. Optionally paste a Codex analytics key (a Platform organization API key).
  5. Click Connect.
nOps stores both credentials securely in AWS Secrets Manager. Keys are checked for completeness on save; live verification against the workspace APIs is coming shortly, so double-check the key and workspace ID before connecting.

​
Manage your connection

Use Re-validate to check stored credentials without re-entering them, or Disconnect to remove them. Action required usually means a revoked or under-scoped key — create a new Admin key in the Global Admin Console and connect again.

​
Troubleshooting

  • Invalid key — confirm you used a workspace Admin key from the Global Admin Console, not a Platform Admin API key from OpenAI (Platform).
  • Permission errors — the key needs read access to the cost category. Recreate it with the permissions from Create an Admin key.
  • Admin keys unavailable — Admin keys are gated to eligible Business and Enterprise/Edu workspaces. Confirm your plan tier with OpenAI.
  • No data — allow up to 24 hours after connect for usage data to populate in Inform.
  • Codex usage missing — Codex on ChatGPT credits appears here, while Codex on a Platform API key appears under OpenAI (Platform). If your developers use both, connect both integrations.
  • Multiple workspaces — repeat connect with a unique Admin key name per workspace. Keys do not span workspaces.

​
Security

Follow your organization’s key rotation policy. Update nOps before rotating keys in the Global Admin Console to avoid sync gaps.