Question 1

Does Ana respect Confluence permissions?

Accepted Answer

Yes. When you use per-user OAuth, every API call Ana makes runs under the identity of the user asking the question. Space and page restrictions configured in Confluence are enforced by Atlassian on the server side, so Ana cannot surface pages the user could not otherwise access.

Question 2

Can Ana use CQL to search Confluence?

Accepted Answer

Yes. The connector supports the full Confluence Query Language for advanced searches. Ana can construct CQL queries to filter by space, label, author, modification date, and more, then bring the results back into its analysis alongside warehouse data.

Question 3

How are Atlassian credentials stored?

Accepted Answer

OAuth refresh tokens and API keys are encrypted in TextQL's credential vault and injected into requests by our egress proxy. Ana's Python sandbox never receives the raw token. Refresh cycles happen outside the sandbox and are fully audited.

Question 4

Can I connect both Confluence and Jira?

Accepted Answer

Yes. Confluence and Jira are separate products under the Atlassian umbrella, and TextQL supports both with independent connector configurations. You can use one OAuth flow to authorize both if desired, or configure them separately with distinct scopes.

Question 5

Is Confluence content cached?

Accepted Answer

By default no — Ana fetches live content each session so answers reflect the latest edits. Optional short-lived caching can be enabled per connector to speed up multi-step analyses without introducing stale results beyond the session.