{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":17880,"path":"governance-risk-compliance/privacy-workspace/access-control-by-legal-entity.md","title":"Accessing control through organizational structure","bundle":null,"doc_type":null,"release":"australia","body":"\n# Accessing control through organizational structure\n\nAccess to processing activity records can be restricted by using Entity-Based Access \\(EBA\\).\n\nUser access to processing activity records and related data can be restricted based on an organizational structure. This structure may reflect a legal entity, jurisdiction, business unit, or any segmentation aligned with how your privacy teams operate. This approach enables granular security and supports regulatory compliance for organizations functioning across multiple regions or subsidiaries.\n\nEntity-Based Access \\(EBA\\) implements this control by enforcing data segregation according to the defined organizational structure. With EBA, users can only view and manage records for the entities or jurisdictions to which they have been explicitly granted access. Records outside this defined scope remain hidden.\n\n## Key characteristics\n\n-   Dynamic segmentation: Access can be assigned based on the organizational structure, such as legal entity, jurisdiction, business unit, or any defined grouping. So processing activity records are only visible to the appropriate teams.\n-   Regulatory alignment: Access controls can be mapped to organizational structures, helping organizations meet local regulatory requirements and maintain clear audit trails.\n\nFor information about configuring access control, see [Configuring access control](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/privacy-workspace/configure-access-control-by-legal-entity.md).\n\n## UI impact\n\n-   Processing activity details: Hidden for records outside the user’s scope.\n-   Data lineage: Information for inaccessible entities is hidden, and navigation buttons on the side panel are disabled.\n-   Reports and dashboards: Visibility in reports such as processing activity, risk scan, and compliance is filtered based on entity configuration.\n\n## Role capabilities\n\n<table id=\"table_gyj_m5m_lhc\"><thead><tr><th>\n\nRole\n\n</th><th>\n\nCapabilities\n\n</th></tr></thead><tbody><tr><td>\n\nPrivacy admin\n\n</td><td>\n\n-   Create entity configurations\n-   Perform bulk access updates\n\n</td></tr><tr><td>\n\nPrivacy manager\n\n</td><td>\n\nView entity configurations\n\n</td></tr><tr><td>\n\nPrivacy analyst\n\n</td><td>\n\nAccess records for configured entities and their associated downstream entities\n\n</td></tr><tr><td>\n\nPrivacy business user\n\n</td><td>\n\nAccess records for configured entities and their associated downstream entities\n\n</td></tr></tbody>\n</table>**Note:** Assigned roles such as assignee, reviewer, and analyst retain access to their assigned records even if those records fall outside the configured entity.\n\n-   **[Configuring access control](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/privacy-workspace/configure-access-control-by-legal-entity.md)**  \nConfigurie Entity-based access control in Privacy Management, including property activation, hierarchy setup, record mapping, user assignment, bulk updates, and activating entity-based record access rules.\n\n**Parent Topic:**[Using Privacy Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/privacy-workspace/using-privacy-mgmt.md)\n\n"}}