Enabling ChatGPT Enterprise Archiving

Last updated: July 14, 2026

ChatGPT Enterprise — Compliance API onboarding

To enable ChatGPT Enterprise archiving in Hadrius, your team will need to securely provide three values from your ChatGPT Enterprise workspace:

Field

Example

Where it comes from

compliance_api_key

sk-comp-...

Generated when you create a Compliance API key in your ChatGPT Enterprise workspace

workspace_id

workspace_abc123...

Your ChatGPT workspace identifier

organization_id

org-abc123...

Your OpenAI organization identifier

Before you begin

The Compliance API is available for ChatGPT Enterprise and ChatGPT Edu workspaces.

If your organization uses ChatGPT Team or a personal ChatGPT plan, contact your OpenAI account representative. The Compliance API endpoints required for archiving are not available on those plans.

You’ll need access as:

  • A ChatGPT workspace owner to create the Compliance API key and locate the workspace ID

  • An OpenAI organization admin to locate the organization ID

Step 1: Create a Compliance API key

  1. Sign in as a workspace owner at https://chatgpt.com/admin.

  2. Open Compliance → API keys.

    This may also appear as Compliance API under Settings → Data Controls.

  3. Click Create new key.

  4. Give the key a recognizable name, such as:

    Hadrius Archiving

  5. Copy the secret value.

    Important: OpenAI only shows the secret once. Save it securely before closing the dialog.

  6. Confirm the key has permission to read:

    • Conversation message logs

    • User-uploaded files

Hadrius uses these permissions to archive ChatGPT conversation transcripts and related attachments.

Step 2: Find your workspace_id

In the same ChatGPT admin console:

  1. Open Settings → Workspace or Settings → General.

  2. Locate the workspace ID near the workspace name.

  3. Copy the full value.

The workspace ID should begin with:

workspace_

Example:

workspace_abc123...

Step 3: Find your organization_id

  1. Open https://platform.openai.com/settings/organization/general while signed in as an organization admin.

  2. Copy the Organization ID.

The organization ID should begin with:

org-

Example:

org-abc123...

If your ChatGPT Enterprise workspace was provisioned without a linked OpenAI Platform organization, contact your OpenAI account representative. The Compliance API still requires this ID for routing.

Step 4: Send the values to Hadrius securely

Please do not send the Compliance API key over plain email or chat.

Use one of the following secure delivery methods:

  • flashpaper.hadrius.com

  • A shared item in 1Password, LastPass, or Bitwarden

  • Encrypted email using S/MIME or PGP

  • The secure file drop link provided by your Hadrius onboarding contact

Send the values in this format:

compliance_api_key: <key starting with sk-comp-...>
workspace_id:      <workspace_...>
organization_id:   <org-...>

Once Hadrius receives these values, archiving will begin on the next sync cycle, typically within one hour.

You do not need to provide:

  • ChatGPT admin login credentials

  • SSO bypass access

  • Any additional ChatGPT account access

How Hadrius uses these values

Hadrius uses these values only to configure read-only ChatGPT Enterprise archiving.

Value

How Hadrius uses it

compliance_api_key

Stored encrypted in AWS Secrets Manager and scoped to your tenant. Used to call OpenAI’s Compliance API to download conversation message logs and user-uploaded files for the configured retention period.

workspace_id

Scopes API calls to your ChatGPT workspace so Hadrius only accesses data from your workspace.

organization_id

Used for the subset of compliance endpoints that bind to the OpenAI Platform organization rather than the ChatGPT workspace, typically Agent or App data.

Hadrius does not:

  • Post anything to ChatGPT

  • Modify ChatGPT settings

  • Write to your ChatGPT workspace

  • Receive admin login access

The Compliance API is read-only.

Rotating or revoking the API key

You can revoke the Compliance API key at any time from the ChatGPT admin console.

When the key is revoked:

  1. Archiving stops on the next sync attempt.

  2. Hadrius surfaces a clear error to your Hadrius admins.

  3. A new Compliance API key will need to be created and securely shared with Hadrius to resume archiving.