In this article:
ChatGPT Overview
ChatGPT Requirements
How to Connect and Collect using ChatGPT
What Gets Collected
ChatGPT Considerations & Limitations
ChatGPT Overview
Onna's ChatGPT connector allows you to collect and preserve AI conversation data generated by ChatGPT within your organization's OpenAI environment. Onna retrieves this data through the OpenAI Compliance Export API — the purpose - built interface that gives enterprise workspace administrators programmatic access to conversation logs, metadata, and file attachments for eDiscovey, compliance , ad data loss prevention (DLP) purposes. (the administrative interface used to access and export ChatGPT conversation content for enterprise accounts.)
The Compliance API supports two complementary access patterns: the Compliance Logs Platform, which provides immutable, append-only log exports for auditing, and the Stateful Compliance API, which enables querying conversation state at the time of the request. Onna uses both to ensure comprehensive and accurate coverage of your organization's ChatGPT activity.
Once collected, ChatGPT conversations become searchable within Onna, giving your team visibility into AI-assisted interactions across your organization.
Connector Features | |
|---|---|
Authorized Connection Required? Yes | Is identity mapping supported? Yes |
Audit logs available? Yes | Admin Access? Yes |
Supports a full archive? Yes | Custodian based collections? Yes |
Sync modes supported: One-time sync, Auto-sync, Auto-sync and archive | Is file versioning supported? No |
ChatGPT Requirements
To connect and collect ChatGPT Enterprise data in Onna, the following must be in place:
An active ChatGPT Enterprise or ChatGPT Edu subscription with OpenAI
The OpenAI Compliance API enabled for your organization's workspace — contact your OpenAI account team to confirm this is active
An API Key issued by OpenAI for your organization's workspace — this must be requested directly from OpenAI and can be reused across multiple data source configurations
The Workspace ID for the ChatGPT Enterprise workspace you wish to connect
Workspace owner or admin access in OpenAI to manage API credentials and confirm compliance settings
Note
The ChatGPT Enterprise connector is not compatible with ChatGPT Free, Plus, or Team plans. The OpenAI Compliance API is available exclusively to Enterprise and Edu subscribers. If you manage multiple ChatGPT Enterprise workspaces, each workspace requires a separate connection and data source configuration in Onna.
How to Connect and Collect using ChatGPT
The ChatGPT collection process uses the OpenAI Compliance Export API to retrieve conversation data on a per-custodian basis. Here is what happens during a sync:
Step 1 — Authorized Connection Setup
Before running a sync, an authorized connection must be configured in Onna using your organization's OpenAI API Key credentials and Workspace ID. Start by opening the Admin user menu from the top-right corner of the interface. Select Authorized Connections from the menu options.

Choose Enterprise sources as the source type.

From the list of available enterprise connectors, select ChatGPT Enterprise.

Enter your organization's Workspace ID and OpenAI API Key in the fields provided, then click Connect to complete the setup.
.png)
The same API Key can be reused if you are configuring authorized connections for multiple ChatGPT Enterprise workspaces — each workspace will still require its own separate connection entry with its corresponding Workspace ID.

Step 2 — Custodian Resolution
Onna identifies the custodians included in your sync by mapping user accounts from your connected OpenAI workspace. Each custodian is resolved to their corresponding OpenAI user identity. User name and email are resolved at this stage where the user is logged in.
Step 3 — Data Request via OpenAI Compliance API
Onna submits requests to the OpenAI Compliance Export API for each custodian, using the configured date range criteria. Because ChatGPT Enterprise only supports a greater than or equals date operator, the collection retrieves all prompts and responses from the specified start date through to the current date. The API returns all conversations updated on or after that date, including both persistent conversations and ephemeral (temporary chat) sessions that fall within OpenAI's 30-day retention window. Depending on the volume of conversations, this process may take a few minutes to complete.
Step 4 — Download and Ingestion
Once OpenAI returns the exported data, Onna downloads the returned conversation data — including both persistent and ephemeral (temporary) conversations — and parses each thread for ingestion. Attachments such as uploaded files and ChatGPT-generated files are captured alongside conversation content.Each conversation thread is ingested as a standalone item within Onna.
Step 5 — Search and Access
Ingested conversations become searchable within Onna alongside your other collected content. Each conversation thread is ingested as a standalone item that can be reviewed, tagged, and exported independently.
Note
Ephemeral chats — conversations where OpenAI's Memory feature is disabled and the session is not saved to the user's history — are also captured via the Compliance API, provided they fall within OpenAI's 30-day retention window for deleted and temporary data. These conversations do not appear in the end user's ChatGPT history but are included in Onna if the date filters are appropriately configured.
What Gets Collected
Onna collects ChatGPT Enterprise AI conversations as dedicated conversation resources. Each conversation thread is ingested as a standalone item that can be searched, reviewed, and exported independently.
Content | Details |
|---|---|
Conversation threads | The full exchange between a user and ChatGPT, including prompts and responses, preserved in chronological order. |
Participants | The workspace user(custodian) associated with the conversation, including user ID, name, and email address(when the user is logged in) |
Timestamps | Individual timestamps for each prompt and each response within a conversation. |
Model information | Metadata identifying the GPT model version used during the conversation. (e.g., GPT-4o, GPT-4 Turbo) |
Conversation title | The title assigned to the conversation, either by the user or auto-generated by ChatGPT. |
Edit history | When a user edits a prompt, the revised message is captured as a new entry in the conversation thread.The original prompt and its subsequent responses are preserved alongside the edited version. |
Source attributions | URLs of publicly cited websites referenced by ChatGPT when web browsing was enabled during the conversation. |
Attachments | Files uploaded by the user during the conversation (e.g., PDFs, DOCX, images, CSVs) and files generated by ChatGPT in response to prompts. |
Note
User prompts and ChatGPT responses are clearly distinguishable within each collected thread, preserving the conversational structure for review. Both persistent conversations and ephemeral (temporary) chats are collected, subject to OpenAI's retention window.
Threads are generally preserved in the correct prompt-then-response order. Where the Compliance API returns a response timestamped before its prompt, Onna auto-corrects ordering if the gap is under 1 second. For larger gaps, the API-provided ordering is kept as-is, which may result in some threads appearing out of sequence.
ChatGPT Considerations & Limitations
Enterprise Subscription Required
The ChatGPT Enterprise connector is only compatible with ChatGPT Enterprise and ChatGPT Edu accounts. Organizations using ChatGPT Free, Plus, or Team plans do not have access to the OpenAI Compliance API and cannot use this connector.
Compliance API Must be Enabled
The Compliance API is not automatically active for all Enterprise accounts. Your organization must confirm with OpenAI that the Compliance API has been enabled for your workspace before configuring the connection in Onna. For instructions on how to enable the API and generate your API token, visit the OpenAI Compliance Platform page.
30-Day Retention Window for Deleted and Temporary Data
OpenAI retains deleted conversations and ephemeral (temporary) chat data for a maximum of 30 days, unless legally required otherwise. Ephemeral chats — sessions where the user's history is not saved — are accessible through the Compliance API but only within this 30-day window. Content outside this window is not retrievable.
Date Filtering Limitation
ChatGPT Enterprise only supports a greater than or equals operator for date-based filtering. When configuring a collection, setting a start date will return all prompts and responses from that date through to the current date. Filtering to a specific date range with a hard end date is not supported at the API level.
Note
Date filters apply at the message level, not the conversation level. If a conversation was created before your specified start date but contains messages sent after it, only those messages will be captured. Some collected conversation threads may therefore appear incomplete, as earlier messages outside the selected time frame will not be included.
Multiple Workspace Support
If your organization has more than one ChatGPT Enterprise workspace, each workspace requires its own authorized connection and data source configuration in Onna. Onna recommends clearly naming each data source to distinguish between workspaces.
Custom GPTs
Conversations conducted using custom GPTs built within your organization's workspace are captured via the Compliance API alongside standard conversations. Coverage of third-party or externally published GPTs may vary depending on how those interactions are stored in OpenAI's backend.
Shared Conversations
Conversations shared between users via OpenAI's sharing feature are associated with the originating custodian. If a recipient branches a shared conversation —continuing it as their own thread — OpenAI treats this as a new independent conversation in the API. In this case, the same original conversation may appear under multiple custodians, each with their own branched version collected as a separate item.
No Real-Time Collection
The ChatGPT Enterprise connector does not support real-time or near-real-time collection. Content captured during a sync reflects what was available through the Compliance API at the time the request was submitted.
Note
OpenAI makes 99% of conversations available via the Compliance API within 30 minutes of being sent.
Content Format
Conversation content is ingested as structured text. Code blocks, lists, and other rich formatting generated by ChatGPT are preserved to the extent provided in the Compliance API response payload.