Every table, schema, field, and database you sync into the catalog gets its own asset details page. From there you can see what the asset is, who owns it, whether it has been reviewed, and how it connects to other data in your pipelines. This page walks through the tabs you will see, what the Overview tab shows, and how to edit an asset's governance metadata.
Overview
Open any asset from the Data Catalog to land on its details page. The page is organized into tabs, and the tabs you see depend on the kind of asset you are looking at — a database shows different information than a single field. Governance information such as tags, classifications, glossary terms, owners, and certification status lives on the Overview tab and can be edited from there at any time.
Asset tabs by type
The tabs available on an asset's details page change based on what kind of asset it is:
Database assets show Overview, Schema, and Table tabs, so you can drill from the database down into its schemas and tables.
Schema assets show Overview and Tables tabs.
Table assets show Overview, Fields, and Lineage tabs.
Field assets show Overview and Lineage tabs.
Because lineage is explored from tables and fields, databases and schemas act mainly as containers you navigate through rather than places you trace data flow from. There is no separate Quality tab on an individual asset — quality scan results live in the Data Quality module instead.
The Overview tab
The Overview tab is organized into three groups of information:
About — the asset's description plus quick facts pulled from the source system: record count, field count, size, primary key, last updated date, source schema, and connection.
Governance — the asset's certificate status (Verified or Not Verified), its owners, tags, classifications, and glossary terms.
Collaboration — the people involved with the asset.
Below these groups, an Upstream/Downstream summary gives you a quick read on how the asset connects to others, with a View Graph link that opens the full picture on the Lineage tab.
The Fields tab
For table assets, the Fields tab lists every column the sync discovered, showing each field's name and its source data type — such as int, varchar, or date — alongside its own governance metadata. Each field is actually its own asset: click into any field to see its Overview, including its field type, the table it belongs to, any foreign key relationships, and its own field-level Lineage.
Editing tags, classifications, glossary terms, and owners
To update an asset's governance information, open the asset and choose Edit. From the edit form you can set:
Description — the "About this table" summary shown on the Overview tab.
Classifications — labels for the sensitivity or category of the data.
Tags — free-form organizational labels.
Glossary — links to your organization's defined business terms.
Owners — the people accountable for the asset.
Shared With — who else has access to it.
Each of these fields is a multi-select picker, so you can attach more than one value where it applies. The asset's name is read-only, since it mirrors the source system — you cannot rename it from the catalog. Tags are required before you can save changes.
Once you save, you will see a message confirming the update succeeded. Governance changes are applied asynchronously, so give it a moment before the update is reflected everywhere in the catalog.
Classifications, glossary, and certificates explained
Classifications, glossary terms, and certification serve different purposes, though together they make an asset easier to trust and easier to find:
Classifications label the sensitivity or category of data, supporting policy enforcement and discovery.
Glossary terms connect the asset to your organization's defined business language, so people can find data by familiar terms rather than technical names.
Tags are flexible, free-form labels you define for your own organizational needs.
Certificate status shows whether an asset has been reviewed. Verified assets display a green badge throughout the catalog, signaling to anyone browsing that the data can be trusted.
Together, these governance fields turn a synced table into a catalog asset that people can confidently find, understand, and rely on.
Notes
Asset names are always read-only in the catalog — rename them at the source system instead.
Tags are mandatory on the edit form; you cannot save changes without at least one tag.
Governance updates apply asynchronously, so recently saved changes may take a little time to show up everywhere.
There is no per-asset Quality tab — check the Data Quality module for scan results.