> ## 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.

# FAQ

> Answers about OrgX capabilities, developer surfaces, access, and data boundaries.

## Product

> [accordion] What is OrgX?
>
> OrgX is an operating record for AI-delivered work. It connects initiatives,
> decisions, artifacts, approvals, and execution receipts so supported AI
> clients and people can work from the same workspace context.

&#x20;

> [accordion] Who is OrgX for?
>
> OrgX is designed for solo technical founders, small teams, and product or
> engineering leaders who need agent work to remain reviewable across tools. The
> best fit is work that has meaningful handoffs, approvals, or evidence
> requirements.

&#x20;

> [accordion] How is OrgX different from using an AI client alone?
>
> An AI client provides the interaction surface. OrgX provides the shared
> workspace record: work hierarchy, decisions, artifacts, access boundaries, and
> receipts. [Contract principles](https://docs.useorgx.com/docs/concepts.md#contract-principles) explain what
> state and evidence mean across those surfaces.

> [accordion] Is OrgX ready for production use?
>
> The published REST operations and MCP surfaces are documented for real
> integrations. Use the contract and availability pages for the behavior of
> each surface, keep authenticated tests in a dedicated workspace, and review
> consequential actions before enabling broader autonomy.

## Agents and control

> [accordion] What can agents do?
>
> Depending on the connected surface and granted permissions, agents can read
> context, analyze work, draft artifacts, create or update connected-tool
> records, and propose decisions. The active MCP tool catalog and integration
> guide are authoritative for what is callable in a given client.

&#x20;

> [accordion] What does a person still control?
>
> Workspace authorization, integration scopes, autonomy settings, and decision
> checkpoints control what agents may do. A producer receipt is not proof of
> acceptance or an external outcome; review records and evidence remain separate
> states.

> [accordion] Can I customize agent behavior?
>
> Use workspace autonomy settings, tool scopes, budgets, and supported skill
> or plugin configuration. See [Decisions](https://docs.useorgx.com/docs/platform/decisions.md) and
> [Skills](https://docs.useorgx.com/docs/platform/skills.md) for the surfaces available to your client.

## Integrations

> [accordion] Which integrations are documented?
>
> Linear is documented as an available integration. GitHub is documented as a
> beta integration. Stripe is documented for billing and the Content Studio
> callback boundary. Slack, Notion, HubSpot, Figma, and Mailchimp are not
> native OrgX integrations in the current guide. See
> [Integrations](https://docs.useorgx.com/docs/guides/integrations.md) for scope and permissions.

&#x20;

> [accordion] Can I use OrgX without Linear?
>
> Yes. Start with the web app, [AI Toolkit](https://docs.useorgx.com/docs/guides/toolkit.md), OpenClaw, ChatGPT
> (through the ChatGPT plugin directory), or the hosted MCP endpoint. Add
> external integrations only when their documented permissions match your
> workflow.

> [accordion] How do I disconnect an integration?
>
> Use **Settings → Integrations → Disconnect** in the OrgX application. This
> removes OrgX's access; it does not imply deletion of historical records
> already stored in the workspace.

## ChatGPT and MCP

> [accordion] How do I connect OrgX to ChatGPT?
>
> OrgX is listed in the ChatGPT plugin directory. Open the
> [OrgX listing](https://chatgpt.com/plugins/plugin_asdk_app_6a1083cac4788191a47b657dc58c4315) or search for **OrgX** under Plugins in ChatGPT, choose
> **Connect**, and approve your workspace. The
> [ChatGPT integration guide](https://docs.useorgx.com/docs/guides/chatgpt-integration.md) covers the
> Developer Mode fallback for workspaces that block directory plugins.

&#x20;

> [accordion] What is MCP?
>
> The Model Context Protocol is the interface used by compatible AI clients to
> call OrgX tools and read OrgX resources. See the [MCP protocol
> reference](https://docs.useorgx.com/docs/api/mcp-protocol.md) for endpoint, authorization, and transport
> details.

> [accordion] Can I use OrgX in Cursor or another MCP client?
>
> Yes, when the client supports the documented MCP transport. Start with the
> [AI Toolkit guide](https://docs.useorgx.com/docs/guides/toolkit.md) or the [MCP client setup guide](https://docs.useorgx.com/docs/guides/cursor-mcp-setup.md).

## Billing and privacy

> [accordion] Where can I find current pricing?
>
> See the [current pricing page](https://useorgx.com/pricing). This
> documentation does not repeat plan amounts because pricing and entitlements
> can change independently of the API contract.

> [accordion] Where can I find security and privacy details?
>
> Read [Security](https://docs.useorgx.com/docs/resources/security.md) and the application's
> [Privacy Policy](https://useorgx.com/privacy). Do not put credentials,
> payment details, or private workspace data in public validation requests or
> support tickets.


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