Glossary
Access level
Section titled “Access level”Who may call an operation: logged in, any member, or owners and admins (Authentication).
Active workspace
Section titled “Active workspace”The workspace every /v1/ call acts on. Each session has one; switch it with
POST /api/auth/organization/set-active.
Bridge
Section titled “Bridge”How a generated UI’s queries reach the API: the document asks the page that shows it, and the page calls the API (Embedding generated UIs).
Connector
Section titled “Connector”A data source a workspace queries in place: a PostgreSQL database, or a BigQuery project. Its alias is the
name used in SQL, for example crm in crm.public.orders. Its password or key is stored encrypted and never
returned.
Conversation
Section titled “Conversation”A series of questions and answers (or chat messages) of one user in one workspace. Only its author can read it.
Generated UI
Section titled “Generated UI”A dashboard written by the language model from a prompt: an HTML document plus the saved queries it may run. Each change makes a new version; older versions keep working.
The workspace’s own storage, with the tables that sync jobs copied in. Its tables are named lake.<table>.
Live source
Section titled “Live source”A connector queried in place, at the moment of the question. A BigQuery connector is live only when created
with live: true; every read is then billed by Google.
Metric
Section titled “Metric”A named measure in a table description, with a definition in words and a formula such as sum(amount).
The formula is a hint for the model; it is never run.
Owner, admin, member
Section titled “Owner, admin, member”The roles of a workspace membership. Owners and admins manage connectors, descriptions and sync jobs; members use them.
Saved query
Section titled “Saved query”A checked, stored SELECT with declared parameters, run by name with parameter values. Clients see its name and
parameters, never its SQL. Generated UIs create them.
Server-sent events
Section titled “Server-sent events”How long calls answer: a stream of named events (Streaming responses).
Source
Section titled “Source”Anything a workspace can query: the lake, or a live connector. GET /v1/sources lists their tables and columns.
Sync job, sync run
Section titled “Sync job, sync run”A sync job copies a database table or an uploaded file into the lake on a schedule; each run of it is a sync run, with its status and row count.
Table description
Section titled “Table description”What a table, its columns and its metrics mean, written by owners and admins. The model reads them when it answers questions and builds UIs.
Workspace
Section titled “Workspace”The unit of tenancy: one team or company, with its own sources, lake, descriptions, conversations and UIs. Data never crosses from one workspace to another.