Policy Enforcement in Data 360

Policies are enforced across different feature areas in Data 360 depending on whether the user is creating or consuming data. Policy enforcement doesn't take effect immediately in dashboards.

To ensure policies are applied correctly, refresh the dashboard or clear the cache.

• Policy Behavior When Creating Data Streams and Data Objects
  When you create data streams, data lake objects (DLOs), or data model objects (DMOs), Data 360 enforces access policies to make sure you can only interact with the objects and fields you're allowed to use.
• Policy Behavior When Consuming Data Streams and Data Objects
  When you view or work with data objects in Data 360, access policies determine what you can see and use.
• Policy Behavior When Querying Data
  When you query data in Data 360, whether through Data Explorer, Profile Explorer, or Tableau, governance policies control what you can retrieve. Even if metadata is visible in the UI, actual access is enforced at query time to protect sensitive data.
• Policy Behavior on Process Definitions
  Data 360 process definitions describe the workflows and tasks used to manage data such as data streams, transformations, calculated insights, segments, and identity resolution. These definitions help standardize how data operations are created and executed. Data governance policies are enforced when users create or consume these definitions.
• Policy Behavior on Core Applications in Data 360
  Core applications such as Related Lists and Copy Field Enrichment follow specific policy behaviors. While some features honor user-level access controls, others run in system mode and require additional security measures at the CRM level.