Lineage
Object and column level lineage can be managed by clicking on lineage icon 
, found after object/attribute name. Green icon indicates that some lineage relations have already been set. New relations can be set from Column level relations.
Object level lineage
Object level lineage can be opened from Catalog objects view.
Direct relations
By clicking on Columns chevron
for any of the objects found on the lineage graph, a list of all active columns for selected object is displayed, with direct relations to any other columns.By clicking on Columns detailed view icon
a detailed view of all columns for selected object is displayed. 
Column relation map
By clicking on any of the relation paths, a column map for selected relation will be displayed.
dbt badge
Objects and columns matched to a dbt project display a small dbt badge in the upper-right corner of their node. Clicking the badge opens the dbt Resources browser with the corresponding model, source, seed, snapshot, or exposure pre-selected - useful for jumping straight from a lineage node to its raw and compiled SQL, tests, and manifest metadata.
The badge only appears when the dbt enrichment is still active; nodes whose dbt project has been removed are shown without the badge.
Data quality
By clicking on data quality bar, a Data quality overview will be displayed
Clicking 
icon will redirect to related test cases or profilings
Viewing origin queries
In case of automated lineage you can view the query where lineage originates from by pressing on the 
button. This can be done on object or column level.
From all relations you can view detailed information about queries the relation originates from
For each reference the modal shows Created by and Created at at the top of the relation summary, and each individual reference in the chain also shows its own Created at timestamp under the header. This makes it easy to tell when an automated lineage relation was first picked up and when individual contributing queries were last reimported.
Deleting a single query reference
When an automated relation has multiple contributing query references, you can remove just one of them without dropping the whole relation. Hover over a reference in the chain - a trash icon appears next to the header. Click it and confirm the prompt; the reference is removed and the relation stays in place as long as at least one other reference still backs it. If you remove the last remaining reference the relation itself is deleted.
Use this to clean up references from one-off ad-hoc queries while keeping the relation alive through your stable ETL queries.
Column level lineage
Column level lineage can be opened by clicking on any of the columns in Object level lineage graph, or by clicking on Lineage icon, found after any attribute name in Object detailed view. 
Adding new relations
Open object level lineage to get options of adding new relations
A detailed table view allows users to visually explore and manage column relations. Users can select specific columns and define custom relations between them, specifying the source, connection, schema, and target object.
Open column level lineage to get options of adding new relations
New relations can be added by hovering on any of the columns and clicking on the green Plus icon.
Deleting a relation
To remove a relation, select the column with the existing relation. Clicking on it will open a confirmation modal for deletion.
To remove a relation between columns, hover on the column and click the red minus icon. Clicking on it will open a confirmation modal for deletion.
Lineage actions
Navigation - Graph navigation forward or backward.
Open/close - Expand all column relations.
Export - Possible to export lineage as a PNG or Excel file.
Mass actions
Manage relations button can be found on Objects or Attributes tab sidebar.
Manage relations view allows you to manage all lineage relations between catalog objects in a single view. This includes visibility into their origin and creation dates, making large-scale lineage management more efficient.
Relation origin tracking
The manage relations view includes two columns for tracking where relations originate from:
Origin Type - indicates how the relation was created (e.g. imported, manual, automated)
Origin - provides the specific source reference, such as the import file name or an UUID identifier for relation batch
For file-based imports, the origin is automatically set to the import file name. For automated lineage, the origin references the source query.