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

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  {' '}

  <Accordion title="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.
  </Accordion>

  {' '}

  <Accordion title="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](/docs/concepts#contract-principles) explain what
    state and evidence mean across those surfaces.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## Agents and control

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  {' '}

  <Accordion title="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>

  <Accordion title="Can I customize agent behavior?">
    Use workspace autonomy settings, tool scopes, budgets, and supported skill
    or plugin configuration. See [Decisions](/docs/platform/decisions) and
    [Skills](/docs/platform/skills) for the surfaces available to your client.
  </Accordion>
</AccordionGroup>

## Integrations

<AccordionGroup>
  <Accordion title="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](/docs/guides/integrations) for scope and permissions.
  </Accordion>

  {' '}

  <Accordion title="Can I use OrgX without Linear?">
    Yes. Start with the web app, [AI Toolkit](/docs/guides/toolkit), OpenClaw, ChatGPT
    where remote MCP is available, or the hosted MCP endpoint. Add external
    integrations only when their documented permissions match your workflow.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## ChatGPT and MCP

<AccordionGroup>
  <Accordion title="How do I connect OrgX to ChatGPT?">
    Use the [ChatGPT integration guide](/docs/guides/chatgpt-integration). It
    documents the current Developer Mode or custom-connector path for accounts
    where remote MCP is available. A working private connection is distinct from
    publication in a provider directory.
  </Accordion>

  {' '}

  <Accordion title="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](/docs/api/mcp-protocol) for endpoint, authorization, and transport
    details.
  </Accordion>

  <Accordion title="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](/docs/guides/toolkit) or the [MCP client setup guide](/docs/guides/cursor-mcp-setup).
  </Accordion>
</AccordionGroup>

## Billing and privacy

<AccordionGroup>
  <Accordion title="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>

  <Accordion title="Where can I find security and privacy details?">
    Read [Security](/docs/resources/security) 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.
  </Accordion>
</AccordionGroup>