The Lineage screen (/linhagem) answers two questions every
data team asks sooner or later: "where did this number come from?" and "if I change
this table, what breaks?". The map is built from the SQL of each
visual — it isn't a hand-maintained drawing, it's what is actually running.
What it is#
A live map of the workspace connecting pipelines → Bronze → Silver → Gold → dashboards/reports, plus a reverse impact analysis and a certification (endorsement) flow for official numbers.
What it's for#
- Trace the origin of a number before trusting it.
- Prevent breakage: check what depends on a table before renaming a column or swapping a pipeline.
- Flag what has already been reviewed, with a badge visible to the reader.
Who does it and when#
- It's an owner area: the screen requires
requireOwnerAreabecause the map exposes pipelines and tables from the whole workspace. An invited member is sent back to the BI workspace. - Only the owner endorses certification;
adminand other roles can see it, but can't certify. - Use it before any structural data change and whenever you need to audit the origin of a metric.
What the screen shows#
1. Workspace map
Columns by layer — Pipelines, Bronze, Silver, Gold and external tables — with counts (pipelines · tables · dashboards · reports). Each table shows where it comes from and how many dashboards/reports use it. A badge marks certified tables.
2. Where did this number come from? (lineage of a dashboard)
Pick a dashboard and see, side by side, the visuals, the tables that feed each one (with the layer and whether they're a direct source) and the pipelines behind them. There's a shortcut to open the dashboard.
3. If I change this table, what breaks? (impact analysis)
Pick a table and see the reverse effect: affected dashboards, affected reports, derived tables and pipelines to review. This is what keeps you from finding out on Tuesday that the customer's dashboard stopped working.
4. Certification (endorsement)
Mark dashboards, reports and datasets (tables) as reviewed. The badge appears in the Workspace list and at the top of the dashboard, so the reader knows which number is official. Each certification records who endorsed it and when.
Step by step (impact analysis)#
- Open
/linhagem. - In the "If I change this table, what breaks?" section, select the table.
- Click Analyze impact.
- Review the dashboards, reports, derived tables and pipelines listed.
- Only then make the change — and, if needed, re-certify what changed.
Expected result#
A map that reflects the SQL in production, with usage counts, and an impact analysis that lists everything that depends on a table before you touch it.
Example#
At Comércio Aurora, the owner selects prd_aurora_silver.vendas in the impact
analysis and sees that two dashboards ("Vendas por filial", "Resultado de agosto"), a
weekly report and the table prd_aurora_gold.vendas_por_filial depend on it — so they
warn the team before renaming the valor column.
Limits and costs#
- Opening the screen: R$ 0 — the graph is built from metadata (the visuals' SQL), with no paid query.
- The map covers what has traceable SQL; a dashboard with no visual that has SQL doesn't appear in the lineage.
Security#
- Everything scoped by
workspaceId: one customer's graph never touches another's. - Area restricted to the owner; certification only by the owner.
Common errors#
| Symptom | Likely cause | What to do |
|---|---|---|
| "Nothing to map yet" | no pipeline/dashboard with SQL | create a pipeline and a dashboard that reads from the datalake |
| Dashboard disappears from the lineage | it has no visual with SQL | add a visual that queries a table |
| I can't certify | you're not the owner | ask the workspace owner |
| I was sent to the BI workspace | the screen is an owner area | sign in with an owner/admin account |
Related#
Last reviewed: 2026-09-08.