Help with your next step

Start with a sandbox company

1. Sign in, then create or select your organization. Check the environment badge before every connection or access change.
2. In Settings, choose Intuit Sandbox. An owner or admin connects the intended test company from Companies and completes Intuit consent in the browser.
3. In Assistants, review the client guide and choose only the required companies and read operations. Review each permission before granting access.
4. Complete the client acceptance checklist below using synthetic sandbox records. Production and provider consent require separate human approval.

Connect or reconnect QuickBooks

1. If Connect is unavailable, confirm you are an owner or admin and the selected environment is configured. Ask the operator to check that environment’s Intuit setup and exact callback URL; never share client secrets.
2. For reconnect or revoked status, return to Companies and use the connection control for the intended company and environment. Complete a fresh Intuit consent flow; an assistant grant cannot repair Intuit authorization.
3. For refreshing status, wait for the current refresh to finish, then reload once. If the status persists, ask the operator to investigate before starting another authorization flow.
4. If callback or consent fails, check the signed-in OmniQB account and selected organization, then start again from Companies. Do not reuse callback URLs or paste authorization codes into support messages.
5. After reconnecting, review assistant company access again. An active connection alone does not prove that any assistant can read it.

Assistant setup and missing tools

1. ChatGPT and Claude require the hosted OAuth flow and signed-in client acceptance. Those acceptance steps remain pending. A manual bearer key is not a replacement for their hosted flow.
2. Cursor’s guide uses a dedicated manual grant resolved from a local environment variable. Grok’s guide targets the xAI API, not an established consumer grok.com connector. No client is claimed accepted end to end.
3. For 401, check whether the dedicated grant is expired or revoked and use the approved client authorization flow. For 403 or missing tools, have an owner or admin review company access, active environment and exact read permission; do not broaden all permissions to clear an error.
4. If a tool list is stale, have the client workspace administrator review and refresh the connector’s tools using the official client guide. A listed tool still requires server authorization for each call.
5. For initialization failures, use the approved HTTPS deployment’s /api/mcp endpoint. Ask the operator to check deployment readiness and redacted protocol logs. Never put a bearer value in a URL, chat, screenshot or source control.

Sandbox versus production

1. Sandbox uses Intuit test companies. Production can expose real financial data even when operations are read-only. The Settings switch selects an environment; it does not copy companies, tokens or grants.
2. Review the environment-change confirmation and its access consequences before proceeding. Connect and authorize each environment separately; verify the company identity before the first read.
3. A configured badge is not production acceptance. The operator must verify Intuit production setup, provider client consent, and the unresolved onward-AI-sharing policy before broader use.

Team roles and access

1. Owners and admins manage company connections and assistant grants. Members should ask an owner or admin for the specific access needed. Organization membership and assistant permissions are separate checks.
2. In Team, verify the intended organization and invitation recipient. Expired, used or revoked invitations need an administrator’s review; signing in with another account does not transfer membership.
3. Assistant access is default deny. Per-company overrides replace the default operation list. Review report permissions separately because a report may expose underlying financial data.
4. If access changes while you work, reload and select the organization again. Review any confirmation before changing roles, removing access, revoking grants or disconnecting a company.

Document and upload statuses

1. Reading an existing QuickBooks attachment or PDF is separate from staging a new file. A preview is not a posted document and does not change your books.
2. Reserved means storage is being prepared or its outcome is uncertain. Quarantined means the file is not cleared for proposal use; do not bypass scanning. Clean means the configured scanner cleared those bytes, not that Intuit received the file.
3. Cleanup means deletion is queued. Deleted records indicate confirmed deletion of the staged object; they do not prove deletion from backups or QuickBooks. Never describe queued cleanup as finished.
4. Expired or invalid handles require a fresh authorized staging attempt after the prior outcome is resolved. After an uncertain upload response, do not repeatedly retry with new request IDs; ask the operator to check cleanup.
5. Staging may be unavailable because storage, scanner, cleanup health, permissions or quotas are not ready. Current live upload execution remains disabled. Ask the operator to resolve the gate rather than uploading sensitive documents to troubleshoot.

Unavailable features and proposal previews

1. The Access catalog distinguishes available reads, proposal code with live execution disabled, and gated products. A catalog entry or passing synthetic test is not evidence of live provider acceptance.
2. Financial writes and payments are not enabled. Confirming a proposal preview does not post, send, charge, delete or update anything in QuickBooks.
3. Payments, Payroll and other restricted products need independently verified provider eligibility and integration work. Changing a team role or reconnecting cannot unlock them.
4. For a disabled operation, check the catalog explanation and ask your administrator whether it is supported. Do not substitute a broader grant or a production connection to bypass a gate.

Client acceptance checklist

Acceptance remains pending for ChatGPT, Claude, Cursor and Grok (xAI API). The same checks apply to each client; browser consent and provider grants are human steps.

1. Have the operator approve a reachable HTTPS test deployment and confirm the provider’s current plan and workspace requirements.
2. Use an explicitly approved sandbox company with synthetic records. Review organization, environment, companies and read permissions before completing consent or creating a dedicated manual grant.
3. Verify initialization, tool discovery and one permitted company-information read. Check that a denied company or operation remains inaccessible.
4. Verify cancellation, expiry and revocation stop access. Record client version, deployment revision, date and redacted results with the operator.
5. Keep production use pending until client acceptance and the Intuit onward-AI-sharing review are resolved. Synthetic protocol checks cannot establish provider acceptance.

Get support

Email support@omniqb.com. Review what you share before submitting anything.

Prepare the affected screen, approximate time and timezone, sandbox or production, client name/version, and a redacted error code. Explain the expected result and steps to reproduce using synthetic data.

Do not include credentials, bearer grants, authorization codes, callback URLs, private upload handles, financial documents or customer data. Nothing is collected or sent from this help page.

Official Intuit authorization documentation. Client-specific official references are linked in the guides above.