---
schema_version: "1"
id: 790ffe09bee53cad72583a3e5cc9dd6bfd7a8ea7d5152e123233c975c32c9377
title: Use Unified Lineage
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_use_unified_lineage.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_use_unified_lineage.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 446e945020c8e8b97c99acb53f16da6238f7f9e6a521630112c3164ffbf8c345
description: Explore and interact with the lineage graph to view how your data objects connect. Search for objects, trace upstream and downstream dependencies, and use side-panel details, field-level views, and tag overlays to understand your data flow and governance context.
products:
  - Data 360
release: "264"
---
# Use Unified Lineage

Explore and interact with the lineage graph to view how your data objects connect. Search for objects, trace upstream and downstream dependencies, and use side-panel details, field-level views, and tag overlays to understand your data flow and governance context.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>All Editions</strong> supported by Data 360. See <a href="https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&amp;release=264.0.0&amp;type=5" title="Data 360 is available in several supported Salesforce editions. Some Data 360 features also require additional licenses.">Data 360 edition availability</a>.</td></tr></tbody></table>

 
| User permission needed |   |
| --- | --- |
| To use unified lineage: | Data Cloud Architect permission set |

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note You can view lineage only for objects within data spaces where you have permission to view metadata. If you don’t have View access on an object, that part of the lineage graph stays hidden, which can result in an incomplete graph. To see the full graph, make sure you have the View All Records permission.

Make sure you:

- Have the View Metadata permission for the data space you’re exploring.
- Understand the Data 360 object model. For example, how data streams, data lake objects, data model objects, calculated insights, and activations relate.
- Review your governance tags so you can interpret tag propagation accurately when viewing tag overlays.

1. In Data Cloud, go to **Data Governance** > **Lineage**.
2. Select a data space and object type, then search for an object by name or browse the list.
    
    The graph initializes with the selected object and shows three upstream and three downstream dependency levels.
    
    - Upstream objects represent ingestion or source connections.
    - Downstream objects represent harmonization or activation flows.
3. In the graph, boxes represent data objects and ovals represent processes such as transforms or activations.
    - To view the fields in the object, expand it.
    - To trace dependencies, go to **Actions** > **Highlight Path**.
    - To reveal more upstream or downstream objects, click **+** to expand the dependencies.
    - To re-render the graph, go to **Actions** > **Re-render Graph** to focus on the selected object.
4. To view object details, click on the object to open the side panel.
    - **Details** - Shows the name, type, category, and operational information such as last run status, record count, and schedule of the object.
    - **Tags** - Lists applied governance tags.
    - **Fields** - Lists fields and their tags.
    - **View Record Page** - Opens the object record in a new tab.
5. To view field-level lineage, open a data object node such as a DLO, DMO, or CIO, expand the field list, and select a field to trace its lineage.
6. To overlay governance tags on the graph, select **Show Tags**. This action is useful to confirm how tags propagate across dependencies and detect gaps in policy enforcement.