Question 1

Can Ana read Grain transcripts?

Accepted Answer

Yes. Grain exposes full meeting transcripts and speaker-level detail through its API, and Ana can read them on demand. This lets you ask Ana to find mentions of specific topics, customers, or products across all recorded meetings and join those findings with warehouse data.

Question 2

Does Ana access Grain highlights?

Accepted Answer

Yes. Ana can read highlights, stories, and tags created by your team in Grain. This is especially useful for surfacing curated snippets alongside warehouse metrics, so you can quickly connect customer feedback to measured business impact.

Question 3

How are Grain tokens secured?

Accepted Answer

OAuth tokens and API keys are encrypted at rest in TextQL's credential vault and injected by our egress proxy at the network layer. Ana's Python sandbox never sees the raw token value. Token refresh happens transparently outside the sandbox and is fully audited.

Question 4

Can I limit Ana to specific workspaces?

Accepted Answer

Yes. Grain API tokens are scoped to a workspace, and admins can connect multiple workspaces with different scopes. You can also whitelist only api.grain.com in the TextQL admin console to prevent Ana from making any unrelated outbound calls.

Question 5

Does Ana respect Grain privacy settings?

Accepted Answer

Yes. Meetings marked private or restricted in Grain are only accessible to users authorized in Grain itself. When using per-user OAuth, Ana inherits the calling user's Grain permissions so private meetings stay private unless explicitly shared.