Question 1

Does Ana use Salesforce permissions?

Accepted Answer

Yes. When you connect Salesforce via per-user OAuth, every API call Ana makes runs under the logged-in user's Salesforce identity. Row-level sharing rules, field-level security, and object permissions are all enforced by Salesforce itself. Ana cannot see records the user could not see in the Salesforce UI.

Question 2

Can Ana write to Salesforce?

Accepted Answer

By default the connector is read-only. Admins can grant write scopes during OAuth setup if you want Ana to update records, create tasks, or log activities. All writes are audit-logged and can be restricted to specific objects or sandboxes. Most teams start read-only and expand write access deliberately.

Question 3

How is the domain whitelisted?

Accepted Answer

An admin adds your Salesforce My Domain and login.salesforce.com to the API connector allowlist in the TextQL admin console. Ana's Python sandbox can only make outbound requests to whitelisted hosts, so there is no risk of data exfiltration to untrusted endpoints.

Question 4

Where are tokens stored?

Accepted Answer

OAuth tokens are stored encrypted in TextQL's credential vault and injected into outbound HTTP requests at the network layer. Ana's Python code sees placeholder variables, never the raw token. Token refresh happens transparently outside the sandbox.

Question 5

Is this SOC 2 compliant?

Accepted Answer

Yes. The API connector runs inside TextQL's SOC 2 Type II compliant infrastructure. All calls are logged, credentials are encrypted at rest and in transit, and customer data is isolated per tenant. Enterprise customers can also deploy TextQL in their own VPC for additional control.