Sigma for dashboards
Dashboards that get to the answer
Reference data
Fix reference data without a ticket
Hand the mapping table to the people who own it, and every edit writes back to the warehouse under existing controls.
Schedule demoWhat the current mapping setup costs
What the current cycle costs
Each number below comes from a customer describing the process they run without Sigma.
11-13Spreadsheets, same purpose
1Input Table every report reads
$240KYearly reference data spend
$0Added to what you already run
110,000Products remapped weekly
0Tickets to remap a product
How it works
3 steps to update a definition
- 1Load the list
Start from an empty Input Table, a CSV upload, or a table already in the warehouse.
- 2Give owners access
Row-level security from the warehouse decides who edits which rows. Nobody sees data they shouldn't.
- 3Publish and audit
Approved edits write back to the warehouse, and audit history on Input Tables records every change.
Load the list. Give owners access. Publish and audit
Taxonomy, not guesswork
Product names resolve to one family
Meridian USB Cable E396
Meridian USB Cable W294
Meridian Ethernet C350
Meridian Ethernet E883
37 SKUs with no L2 family
Certified definition94% certified
Cables
L2 family under Accessories
Owner assignedIn reviewAudit history on
An owner assigns the family once on the Master SKU list, and every report and app reads that assignment.
Owners keep the list current
01Explore
Input Tables under warehouse controls
An Input Table is a warehouse object, so the mapping lives where the models live. Sigma never modifies production tables, and your dbt models stay the source of truth.
- Write only to a designated schema, outside production tables
- Inherit row-level security straight from the warehouse
- Query dbt models directly, with no duplicate semantic layer
02Act
Every definition gets an owner
Certification badges mark a definition endorsed or deprecated, and version tags record the release it belongs to. Actions route each proposed change to the owner who signs it off.
- Mark a definition endorsed, warning, or deprecated
- Let owners edit values without opening a ticket
- Route proposed changes through approval with Actions
03Govern
Every report reads the same list
Change a mapping once and every workbook, report, and app that reads it returns the new value on the next query. Value lists keep the same options in every control.
- Update a mapping once and every report follows
- Upload a starting list of up to 1 GB by CSV
- Reuse the same value list in every filter and form
Connections
Always on the newest trusted data
Sigma queries your warehouse live, so a workbook reads what landed a moment ago.
Governance your data team already set
Reference data edits run under the same roles, permissions, and logs that govern the warehouse itself.
Change historyAppend only
DWCategory manager edited Description on AC-NW-000000185214:22
MEData steward approved Status on AC-NW-000000185314:09
ROReviewer reassigned Owner on AC-NW-000000185413:51
JTData steward set Category on AC-NW-000000185211:04
No shadow copies
Queries run live on the warehouse, and edits insert rows instead of overwriting production tables.
Row-level access
Each person edits the rows their warehouse role allows, so one region owner cannot touch another.
A full change log
Audit history on Input Tables records who changed a value and when, so a dispute ends with evidence.
3 reference data apps to start from
These 3 examples keep definitions, metrics, and metadata in Sigma instead of a side spreadsheet.
Data Catalogue & Metadata
Lightweight data catalogue and governance app. Asset catalog, documentation, quality reporting, audit trail, and access requests.
Data Modeling
Sigma's flexible semantic modeling. Build reusable, secure data models that balance governance with self-service exploration.
Metric Process
Track multiple metrics on the fly and create custom views for end users in a single data app.
Every kind of app
Sigma for every kind of app
All 7 build on the same live, governed platform.
Reference data questions
Give the queue back to owners
Once owners maintain their own definitions, the data team stops maintaining lookups and gets back to shipping models.
Schedule demoActivate your data warehouse
Stop buying a new tool for every workflow. Build it once on governed data, then scale it across the business.