Question 1

Does Ana execute LookML queries?

Accepted Answer

Yes. Ana can run inline queries against LookML explores, execute saved looks, and fetch dashboard data through the Looker API. This means Ana can leverage your semantic layer for definitions while still joining the results with ad-hoc warehouse queries.

Question 2

Are Looker user attributes respected?

Accepted Answer

Yes. When Ana uses a Looker API session tied to a specific user, user attributes and access filters are enforced by Looker itself. This means row-level security and department filters configured in Looker automatically apply to what Ana can see.

Question 3

How are Looker credentials secured?

Accepted Answer

Client ID and secret are encrypted in TextQL's credential vault and injected by our egress proxy at the network layer. Ana's Python sandbox never sees the raw values. Credentials can be rotated any time from the TextQL admin console without changing prompts.

Question 4

Can Ana create Looker content?

Accepted Answer

Yes with write permissions. By default the connector is read-only. Admins can enable write permissions to let Ana create or update looks, dashboards, or schedules. Write operations are audit-logged separately and can be restricted to specific folders.

Question 5

Does this work with Looker Studio?

Accepted Answer

No — Looker and Looker Studio are different products. Looker Studio has its own separate connector in TextQL. This connector targets the Looker (formerly Looker classic) enterprise BI platform with its own API and semantic layer.