Verify the boundary. Keep an undo path.

Use this checklist before connecting, before sending a question, and when your test is complete.

Each step pairs practical guidance with a concrete verification or undo action.

Start with the supported boundary

Test OrgMate with a supported Sandbox, verify that the approval request is for api and refresh_token, and do not paste credentials, OAuth codes, tokens, or customer record data into questions.

Verify: compare the request with those two literal scope names before continuing. Stop if an additional explicit scope appears.

Check what the scope permits and what OrgMate sends

The Salesforce api scope is technically broad enough to permit record access. OrgMate uses it only to retrieve and analyze supported Salesforce metadata. It does not access Salesforce customer record data.

For LLM processing, OrgMate sends OpenAI the relevant user question, OrgMate instructions, and selected context needed for the task. OrgMate does not retrieve, store, or send Salesforce customer record data.

Verify: review the question before sending it. Remove credentials, OAuth codes, state values, tokens, and customer record data.

Recover without sharing OAuth material

If Salesforce blocks the connection, return to OrgMate and ask your Salesforce administrator to check the app’s current access policy. Do not share OAuth codes, state values, or tokens.

Recover: return to OrgMate, ask for the policy check, and retry only after the current org-side access decision is confirmed.

Disconnect and make the provider-side check separate

Disconnecting deactivates the connection in OrgMate even if Salesforce cannot be reached. OrgMate also attempts to revoke the Salesforce refresh token and, where possible, the access token.

For a second provider-side check, follow Salesforce’s current official connected-app revocation guidance.

Undo: disconnect in OrgMate first, then use Salesforce’s current official token-revocation guidance. Do not treat local completion as proof of the remote outcome.