View Asset Relationships and Stakeholders
Learning Objectives
After completing this unit, you’ll be able to:
- Identify direct and indirect asset relationships.
- Locate and manage stakeholders assigned to an asset.
- Explain how ownership and connections drive accountability.
The Asset Details Page
Angela’s colleague Arif Setiawan is Infiwave’s sales associate. He manages the business assets in Cloud Data Governance and Catalog (CDGC) and makes sure every dataset has a clear owner, the right policies applied, and accurate business context.
Arif gets a question from a business user: Is the Customer Name dataset governed by the Personal Data policy?
He knows the answer isn’t always a simple yes or no. Some relationships in CDGC are direct. Others are indirect. Arif opens the asset details page to find out.
When he selects an asset name in CDGC, it opens the Asset 360-Degree View—a detailed page that shows all available information about that asset. This includes:
- Overview (description, stakeholders, classifications, and open tickets)
- Contains (for parent assets)
- Hierarchy
- Lineage
- Relationships
- Stakeholders
- Data Quality
- History
- Tickets
The information shown on the asset details page varies based on the type of asset—business or technical.
Understand Asset Relationships
Arif selects the Relationships tab. The relationships view shows how assets in CDGC are connected to each other. These connections can be:
- Policies governing an asset
- Business terms associated with the asset
- Classifications that identify the asset
- Connections to other datasets, systems, or processes
Relationships can be inbound or outbound. An inbound relationship means another asset is linked to the current asset. An outbound relationship means the current asset is linked to another asset.
Arif can view relationships in two ways.
- Graphical view: A visual diagram showing connected assets and the direction of the relationship. Arrows in the graphical view are color-coded to indicate direction: Outbound relationships flow away from the selected asset, and inbound relationships flow toward it. (Verify arrow color labels against the current CDGC version before publishing.)
- Tabular view: A table listing all related assets, their type, and relationship direction—useful for scanning many relationships quickly.
Direct and Indirect Relationships
CDGC supports both direct and indirect relationships. A direct relationship exists when an asset is explicitly linked to another asset—for example, a policy assigned directly to a dataset or a business term tagged to a column. If Policy A is linked to Business Term B, and Business Term B is linked to Column C, then Policy A indirectly affects Column C. Arif can see this indirect chain in the Relationships tab under Related Assets.
This is important for compliance work. Arif doesn’t need to manually link every policy to every technical asset—the indirect relationships handle the bulk of the work.
View Stakeholders
Arif sees that the Customer Name dataset lists Angela as a stakeholder. Stakeholders are the people responsible for an asset. They receive notifications when tickets are raised, and they’re accountable for the accuracy and governance of the asset’s data.
Stakeholders are visible on the dedicated Stakeholders tab of the asset details page. The Overview tab provides a high-level summary of the asset, including its description, classifications, and key metadata. You can also search for assets by stakeholder using the @ symbol in the search bar. For example:
- Business terms with stakeholder @angela.duran
- Policies with stakeholder role @role:data-steward
- Processes without stakeholder
Recap the Key Points
In this badge, you followed Angela and Arif as they navigated data lineage, mapped asset relationships, and identified stakeholders in CDGC. You now have the skills to trace data flows, identify direct and indirect relationships, and understand how ownership drives accountability in your organization.
Ready to put it into practice? Explore the recommended resource and prerequisite badges to build your data governance expertise.
