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.
object type
what users can do
Data Stream
Users with permission to create data lake objects can deploy bundles.
After a successful deployment, the resulting data streams, DLOs, and DMOs are
subject to the policy. If the user who initiated the deployment doesn't have
access to the outputs of the bundle, they can't view them afterward.
DLO
Users can create a new DLO from an existing DLO. The DLOs available for
selection are those permitted by their access policies.
After creating a DLO, users still need permission to see it in the list view,
unless they have View All and Modify All permissions.
DMO
Users can create a new DMO from an existing DMO. The DMOs available for
selection are those permitted by their access policies.
After creating the DMO, users must be granted access to it in order to see it in
the list view, unless they have View All and Modify All permissions.
Users can create DMO relationships from a list of objects and fields that are
permitted by their access policies.
Calculated Insight Object (CIO)
Users with permission to create CIOs can use DMOs as inputs to build their
insights. Policies applied to DMOs can impact the DMOs, fields, and rows that the
users can access when defining a CIO.
After creating a CIO, users can apply tags and define policies to further secure
access to CIO data.
Tags are automatically propagated from a DMO to a CIO if the CIO dimension
fields exactly match the corresponding DMO fields. If the CIO dimension is derived
from a formula, tags aren’t automatically propagated.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.