> For the complete documentation index, see [llms.txt](https://docs.licensemeter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensemeter.com/connectors/chatgpt.md).

# ChatGPT

Match your ChatGPT Enterprise or Business member list against Entra ID with a CSV paste. No credentials, no API.

ChatGPT seats are bought fast and reviewed rarely. Paste a member table or analytics export if your workspace provides one, and LicenseMeter prices every seat held by someone who is disabled, gone or inactive when the pasted data includes activity dates.

Open **Connectors > ChatGPT** in your workspace.

<figure><img src="https://1639979424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLWIsqiRHwXSWQ10QGIRo%2Fuploads%2FNqiodODfBB1aRNet22D3%2Fconnector-chatgpt.webp?alt=media" alt="ChatGPT connector in the LicenseMeter sample workspace"><figcaption><p>LicenseMeter sample workspace. All names, costs and findings shown are demonstration data.</p></figcaption></figure>

{% hint style="info" %}
The screenshot shows sample data, not a live connection or provider consent screen. In your own workspace, the page presents the appropriate connection or import controls.
{% endhint %}

## Setup

{% stepper %}
{% step %}

### Prepare the member data

In ChatGPT workspace settings or analytics, use a member table or CSV export if it is available for your workspace. Include the header row so LicenseMeter can detect the available columns.

[OpenAI: Managing members in ChatGPT Enterprise](https://help.openai.com/en/articles/8266401-managing-members-seat-types-roles-and-access-in-chatgpt-enterprise)
{% endstep %}

{% step %}

### Paste it

On the ChatGPT connector page, paste the table or export. Email is required; name, seat type, status and last activity are detected when those columns are present. Comma, semicolon and tab formats all work.
{% endstep %}

{% step %}

### Price the seats

Set your per-seat price under Licenses & prices (chatgpt:) so findings carry your real numbers. Re-import any time. Each paste replaces the previous snapshot.
{% endstep %}
{% endstepper %}

## Data used

* Only what is in your paste: member emails, names, seat types, and status or last-active dates when included

## Outside this connector's scope

* Conversations, prompts or anything inside ChatGPT: no ChatGPT credentials are stored at all

## Findings and limitations

* ChatGPT seats held by accounts that are disabled in Entra ID.
* Seats with no matching directory account at all.
* Seats with no activity for your inactivity threshold, only when the pasted data includes a last-active column.

Activity-based findings require activity dates in the pasted data. A member list without those dates can still support directory matching, but does not establish inactivity.

After setup, check the refresh timestamp and [set contract prices](/licenses-and-prices.md) for any seat-based products. If validation or sync fails, start with [Troubleshooting](/troubleshooting.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.licensemeter.com/connectors/chatgpt.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
