---
sourceDocument: Brazil Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/governance-risk-compliance

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Understanding Processing activity hierarchy

# Understanding processing activity hierarchy {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Track how personal data flows across vendors, applications, and systems within and beyond a processing activity to identify and mitigate privacy-related risks.

Each processing activity can involve multiple entities such as vendors, applications, and systems that together make up the processing activity. These vendors, applications, and systems share data with each other, making it essential
to establish a lineage that tracks where personal data is shared. This understanding helps organizations identify and mitigate privacy-related risks.

## Scenario to understand the importance of Hierarchy {#processing-activity-hierarchy__section_rdj_ncf_ccc}

To understand why lineage is important, consider the following example of a Talent Screening processing activity:

* A candidate registers on the careers portal and submits their resume.
* The candidate's data is fed into SHL, an application used to conduct online assessments, to shortlist candidates.
* Candidates who clear the SHL assessment have their data shared with HireVue for interviews.
* Simultaneously, cleared candidates' data is shared with Tableau for analytics purposes.
{#processing-activity-hierarchy__ul_ygf_h5x_43c}

By establishing a lineage for this processing activity, the organization can track where each piece
of personal data originates, how it is processed, and where it is shared. This visibility helps identify potential privacy risks, such as unauthorized access or data breaches, at any point where personal data is exchanged. With a
clear lineage in place, the organization can ensure it is aware of all points where personal data flows and can implement appropriate safeguards to mitigate privacy-related risks.

## Lineage maps and data transfers {#processing-activity-hierarchy__section_lineage_and_transfers}

Each relationship that you define in a hierarchy is rendered as a lineage map. For more information, see [View lineage map](https://www.servicenow.com/docs/59ahVt9bV2eqlUFLaG9Owg#hierarchy-tab__section_lineage_map).

When personal data moves between nodes in a hierarchy, privacy teams must track where the data goes, whose data is involved, and which legal safeguards permit each movement. Data transfer records capture
this information on the processing activity. Each record represents a specific movement of personal data from one node to another, across regions. For more information, see [Manage data transfers](https://www.servicenow.com/docs/Vjw1ckLxa8mguiuiUXJWNw "Organizations often transfer personal data between applications, vendors, business units, and regions, which are subject to privacy regulations. Privacy Management captures each movement as a data transfer record on the processing activity to help you comply with privacy regulations.").

## Hierarchies, lineage maps, data transfers, and transfer mechanisms {#processing-activity-hierarchy__section_lnc_rb3_lkc}

{#processing-activity-hierarchy__table_scv_5q1_hkc__entry__2}

| Function | Description |
|-|-|
| Hierarchy | Defines how a processing activity connects to vendors, applications, processes, companies, and other entities. To create a relationship, see [Add relationships to a hierarchy for a processing activity](https://www.servicenow.com/docs/weJyMBCNVAnBbk~o3VoENw "Define new relationships in a hierarchy directly on a processing activity to record how it connects to vendors, applications, systems, and other processing activities across regions. This enables you to track cross-border data transfers and generate a lineage map to visualize data consumption, sharing, and the associated risks for a processing activity."). |
| Lineage map | Renders the hierarchy as a visual map so you can trace how data moves between all connected entities. For more information, see [Manage data lineage](https://www.servicenow.com/docs/aZAckgkMa8P6dejrvp02Bw "Data lineage is the visual representation of the relationships you define in a hierarchy. You can add new relationships directly from the lineage map in a processing map."). |
| Data transfer | Captures each distinct movement of personal data from one node to another. |
| Transfer mechanism | Associates every data transfer with a legal safeguard that governs it. |
[ ]

{#processing-activity-hierarchy__table_scv_5q1_hkc}