> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# ChatGPT

> Connect OrgX to ChatGPT from the plugin directory, then ask what needs your attention and get answers that link to your records.

Ask ChatGPT what your team decided, what is in progress and what is waiting on
you. OrgX answers from your workspace and links each answer to its record.
OrgX is listed in the ChatGPT plugin directory, so you connect from the
browser. No terminal or Developer Mode is needed.

> [card] [Open OrgX in ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6a1083cac4788191a47b657dc58c4315)
>
> The OrgX listing in the ChatGPT plugin directory.

## Connect

**1. Open the listing**

Open the
[OrgX listing](https://chatgpt.com/plugins/plugin_asdk_app_6a1083cac4788191a47b657dc58c4315),
or search for **OrgX** under [Plugins](https://chatgpt.com/plugins).

**2. Choose Connect**

ChatGPT opens OrgX in your browser.

**3. Sign in and choose the workspace**

Sign in to OrgX. No account yet? [Create one](https://useorgx.com/sign-up)
first. Choose the workspace ChatGPT should use, then allow access. The
screen lists what ChatGPT may read and change; you can reconnect later to
change it.

**4. Return to ChatGPT**

Start a new chat. Name OrgX in your prompts so ChatGPT uses the connection.

## Your first prompt

Copy this into a new chat:

> Use OrgX to show my connected workspace and summarize what needs my attention. Include links to the records. Don't change anything.

**What you should see:** the name of the connected workspace, then the pending
decisions and blocked work that need you, each with a link that opens the
record in OrgX. A new workspace may have nothing waiting yet, and ChatGPT
says so. That is still a working connection.

If the answer does not mention OrgX or has no links, ChatGPT answered without
the connection. See [ChatGPT answered without OrgX](#troubleshooting).

## What you can ask

Reading changes nothing. Changes are in beta; a pending decision changes only
when you choose an option.

| You want to | Ask | Changes anything? |
| - | - | - |
| See what needs you | "What needs my attention in OrgX this week?" | No |
| Recall a decision and why | "Use OrgX to find our pricing decision and the reason we gave." | No |
| Check progress | "Use OrgX: how is the onboarding initiative going, and what is blocked?" | No |
| Review a pending decision | "Open the pending launch decision in OrgX." | Only when you choose an option. Beta |
| Record a decision for review | "Record in OrgX: we are moving onboarding analytics to PostHog." | Saves it for review; it is not approved. Beta |
| Start an existing task | "Use OrgX to start the task Draft launch post." | Yes. Runs under your budget and approval rules and can incur model costs. Beta |

Where ChatGPT shows app panels, decisions and receipts open as interactive
cards. Elsewhere the same answer arrives as text with links.

## Continue in another tool

Everything you read or record lives in your OrgX workspace, not in the chat.
Open any link in OrgX, or ask Claude, Cursor or Codex about the same record
after connecting them from the [client setup guide](https://docs.useorgx.com/docs/guides/toolkit.md).
Picking work up across tools is in beta: it has been verified end to end for
one client pair so far, not for every pair.

## Limits

* ChatGPT sees what OrgX returns for each prompt, not your whole workspace.
* Interactive cards appear only where ChatGPT supports app panels.
* Changes made from ChatGPT are in beta. Writes and recovery do not yet behave
  identically across ChatGPT, Claude, Cursor and Codex.
* A ChatGPT workspace admin can block directory plugins.
* To see exactly what your connection can do, ask: "List the OrgX tools you
  can use." The full list is in the [tool reference](https://docs.useorgx.com/docs/api/mcp-tools.md).

## Other ways to connect

If your ChatGPT workspace does not allow directory plugins, ask a workspace
admin to allow OrgX. If directory plugins are unavailable in your account, you
can add OrgX manually with the ChatGPT profile endpoint:

```text theme={"dark"}
https://mcp.useorgx.com/mcp?profile=chatgpt
```

* **Developer connection:** Settings → Security and login → Developer mode, then [ChatGPT Plugins](https://chatgpt.com/plugins) → plus → Connection. See [OpenAI's plugin documentation](https://developers.openai.com/plugins/deploy/connect-chatgpt).
* **Managed workspace app:** an authorized administrator or member uses Apps → Create after developer access is enabled. See [OpenAI's managed-app guidance](https://help.openai.com/en/articles/12584461-developer-mode-and-mcp-apps-in-chatgpt).

Both manual paths use the same OrgX sign-in as the directory listing.

## Troubleshooting

> [accordion] ChatGPT answered without OrgX
>
> Start a new chat and name OrgX in the prompt, for example "Use OrgX to…".
> If it still answers without links, open the OrgX listing and confirm it
> shows as connected.

> [accordion] OrgX does not appear in ChatGPT
>
> 1. Confirm OrgX shows as connected on its ChatGPT plugin listing.
> 2. If your workspace blocks directory plugins, ask an admin to allow OrgX.
> 3. For a Developer Mode connection, confirm the URL is
>    `https://mcp.useorgx.com/mcp?profile=chatgpt`.
> 4. Start a new chat.

> [accordion] Answers come from the wrong workspace
>
> Open the
> [OrgX listing](https://chatgpt.com/plugins/plugin_asdk_app_6a1083cac4788191a47b657dc58c4315)
> in ChatGPT, disconnect OrgX, then connect again and choose the right
> workspace on the OrgX sign-in screen.

> [accordion] Sign-in fails
>
> 1. Sign out of OrgX in the browser, then choose Connect again.
> 2. Confirm you sign in with the account that belongs to the workspace.

> [accordion] Approving or recording is refused
>
> Changes need a connection whose account can act in that workspace and the
> matching write access. Reconnect and review the access you grant. The
> response names the missing access when a scope is the cause.

## Permissions and security

### Scopes

The consent screen lists requested scopes. Current MCP source checks known,
verified grants against each tool's required scopes; insufficient grants are
rejected with `insufficient_scope`. Discovery can also omit unavailable tools.
Profiles choose a tool surface; they do not grant workspace permissions.

| Scope | Access requested |
| - | - |
| `decisions:read` | View pending and past decisions |
| `decisions:write` | Approve or reject decisions |
| `agents:read` | View agent status and activity |
| `agents:write` | Start agent tasks |
| `initiatives:read` | View initiative details |
| `initiatives:write` | Create and update initiatives |
| `memory:read` | Search organizational knowledge |
| `offline_access` | Issue a refresh token |

> [!WARNING]
>
> Known verified grants are checked at tool execution. Older credentials whose
> granted scopes are unknown retain legacy compatibility; a missing scope list
> must not be treated as a verified read-only grant. Reauthorize when changing
> access. See [OAuth scope enforcement](https://docs.useorgx.com/docs/api/mcp-protocol.md#oauth-scopes)
> and the generated authorization policy for the current source contract.
> Source review alone does not verify the deployed server revision.

> [!NOTE]
>
> The authenticated ChatGPT endpoint is
> `https://mcp.useorgx.com/mcp?profile=chatgpt` and requires OrgX OAuth. For
> no-auth exploration, use the discovery-only public endpoint at
> `https://mcp.useorgx.com/public`; it returns examples and connection help, not
> workspace data.

### Data privacy

* OpenAI processes your ChatGPT messages under its own policies.
* OrgX receives the requests and responses the connection needs, not a copy
  of the whole conversation.
* Every call is authenticated and scoped to your workspace.
* Retention follows the OrgX privacy policy and the provider's policy. This
  page does not promise zero retention.

## Next steps

> [card] [Connect another tool](https://docs.useorgx.com/docs/guides/toolkit.md)
>
> Add Claude, Cursor or Codex and pick up the same records there.

> [card] [Tool reference](https://docs.useorgx.com/docs/api/mcp-tools.md)
>
> Every published OrgX tool, its access and whether it changes data.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.