Once a catalog has at least one synced source, opening it takes you to the Catalog Browser — a split-view screen where you can drill down through a source's structure on the left, search or scan every indexed asset in the middle, and inspect any single asset on the right without ever leaving the page.
Overview
The browser is built around three pieces working together: a left-hand navigation panel, a central asset table, and a details panel that opens on demand. The left panel gives you Sources for managing connections, All Assets for the full searchable table, and an Applications tree for structural drill-down through each connected app. Selecting anything in the table or tree opens its details on the right, so you can keep browsing while you inspect.
Understanding the asset hierarchy
Every asset in a catalog follows the structure of the source system it came from: an application contains databases, a database contains schemas, a schema contains tables, and a table contains fields. The Applications tree mirrors this exactly. Expanding an application loads its databases, expanding a database loads its schemas, and expanding a schema loads its tables — each level loads only when you open it, so the tree stays fast even for large sources.
Clicking any node in the tree — an application, a database, a schema, or a table — filters the All Assets table down to just the assets under that node. This makes the tree the fastest way to browse when you already know where an asset lives, while the table itself is better suited to searching across everything at once.
The All Assets table
The All Assets table lists every indexed asset in the catalog, regardless of type or source, with columns you can use to identify and compare them at a glance:
Asset Name — the asset's name, with an icon indicating whether it's a database, schema, table, or field.
Parent — the asset it sits under, such as a table's schema or a schema's database.
Application — the connected source the asset came from.
Certificates — its verification status, shown as Verified or Not Verified when one has been set.
Last Updated — when its catalog record last changed; a dash means it hasn't been edited since it was created. Hover over the value to see the audit details.
Two more columns, Created On and Last Updated By, are hidden by default but can be added from the columns menu above the table. Use the table's search when you want to find an asset by name across the whole catalog, and use the Applications tree when you'd rather browse structurally.
The asset details panel
Selecting any row in the table, or any node in the tree, opens a details panel alongside the list. The panel's Overview tab shows the asset's description, key facts, and governance metadata. Tables get two additional tabs — Columns, listing their fields, and Lineage, showing a preview of upstream and downstream connections. The panel is meant for a quick look without losing your place in the table; open the asset's full page when you need the complete tabbed view, including the interactive lineage graph.
Filtering the asset list
Beyond drilling down through the tree, the All Assets table supports its own filters — for example, by asset type or by source application — combined with text search. This lets you narrow a catalog with thousands of synced assets down to the exact table or field you're looking for. When you select an application or a parent node in the tree, its matching filter is applied to the table automatically, so tree-based browsing and table-based filtering stay in sync.
Notes
Tree levels load on demand, so expanding a large application for the first time may take a moment while its databases or schemas load.
A dash in Last Updated doesn't mean the asset is stale — it means the catalog record itself hasn't been edited since it was created.
The details panel always shows a preview; for the full lineage graph and complete metadata, open the asset's dedicated page.