Question 1

Which Notion content can Ana access?

Accepted Answer

Ana can read any page or database that the Notion integration has been explicitly shared with. Notion's permission model is share-based, so admins grant access by inviting the TextQL integration to specific pages, databases, or the entire workspace from the share menu.

Question 2

Can Ana write to Notion?

Accepted Answer

Yes, if the OAuth scope allows it. By default the connector is read-only. Admins can enable write scopes during setup to let Ana create pages, update database rows, or append blocks. Most teams start with read-only and add write access for specific workflows.

Question 3

Does Ana index Notion content?

Accepted Answer

No full re-indexing is required. The connector uses Notion's native search and query endpoints at request time, which means results always reflect the current state of your workspace without waiting for a sync job to complete.

Question 4

How is the Notion OAuth token secured?

Accepted Answer

The OAuth token is encrypted in TextQL's credential vault and injected at the network layer by our egress proxy. Ana's Python sandbox never sees the token value. Token rotation and refresh happen transparently outside the sandbox.

Question 5

Can I limit Ana to specific workspaces?

Accepted Answer

Yes. Notion OAuth is scoped to a workspace, and the TextQL admin can connect multiple workspaces with different scopes and permissions. You can also whitelist only api.notion.com to prevent Ana from making any other outbound calls.