The console
The console is the platform's interface. Its navigation is split into five groups — daily work at the top, administration at the bottom.
On this page
What you see depends on your rights. The administration group is open to platform administrators only, and within the other pages every view shows only what your identity is allowed to see in Trino.
Menu items are German
The console ships in German. Items are named as they appear on screen, with an English rendering in parentheses.
Arbeitsbereich (workspace)
| Menu item | Purpose |
|---|---|
| Übersicht (overview) | The landing page: platform state and entry points into the most frequent tasks. |
| Dashboards | Saved queries and metrics as tiles. Every tile runs under the viewer's own identity — two people looking at the same dashboard do not necessarily see the same numbers. |
Daten (data)
| Menu item | Purpose |
|---|---|
| Daten (data) | The browser across catalog, schema and table. Every table links straight to its lineage. The import assistant sits behind “+ Daten hinzufügen” (add data). |
| Suche (search) | Vector, keyword and hybrid search across ingested data. |
| Abfragen (queries) | The SQL worksheet over Trino. Statements classified as read-only run directly; writing statements only after explicit confirmation. |
| Dokumente (documents) | Upload PDF, Word and text. They are extracted, chunked, embedded, and then live as governed tables in the lakehouse. |
| Datenquellen (data sources) | Register external PostgreSQL, MySQL and MS SQL Server databases and import tables from them. |
| Datei-Crawler (fileshare crawler) | Register a mounted directory instead of uploading files one by one. |
| MCP-Ingestion | Pull tabular data from a registered MCP server into the lakehouse. |
| BI-Anbindung (BI connectivity) | The read-only feed for Tableau and other BI tools. Off as shipped. |
KI & Semantik (AI and semantics)
| Menu item | Purpose |
|---|---|
| Kennzahlen (metrics) | The semantic layer: curated metrics and multi-table views with stored, validated joins. |
| Embeddings | The embedding index and its provider. The local model, keyless, by default. |
| KI-Anbindung (AI backend) | The language model behind the chat. With nothing configured here, the assistant does not answer. |
| MCP-Server | Registration of external MCP servers — and the enablement of the tools lavalake itself offers outward. |
Betrieb (operations)
| Menu item | Purpose |
|---|---|
| Überwachung (monitoring) | Health of the services. |
| Audit-Log | The hash chain of accesses, searchable. |
| Herkunft (lineage) | For any table: where its data came from and who touched it. Derived from the audit trail, not maintained separately. |
Verwaltung (administration)
| Menu item | Purpose |
|---|---|
| Nutzer & Rollen (users and roles) | Accounts and roles, against Keycloak. |
| Richtlinien (policies) | Row-access and column-masking policies. They are compiled into Trino's file-based access control and apply to every query there — not only to the ones from the console. |
Items marked “bald”
Some menu items carry that label: the structure is in place, the function follows in a later stage.
The chat
Next to the navigation sits the chat panel with the assistant. It works with your rights, not its own, and every action passes the same check as a click in the interface. What it may do and how it is controlled is covered under The AI assistant.
Applies to: This page describes lavalake 0.16.0. Product and documentation live in separate repositories — when in doubt, what the console shows is authoritative.
Something missing?
If these pages do not answer your question, we will walk through the platform against your own case in half an hour.
Book a demo