You are here:
Enable Data Governance Permissions for Consumption Forecasting Objects
To use Data 360 Data Governance features for Consumption Forecasting, you need to grant access to the impacted objects according to an access policy.
Required Editions
You can select from either attribute-based access control (ABAC) or role-based access control (RBAC). This allows you to have more granular control over your users access to data. Follow instructions in Grant Access to Data Cloud Objects to assign these objects to an available policy.
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited with Sales, and in Agentforce 1 Sales Edition |
Associated Data 360 Objects
| Object TYpe | Name |
|---|---|
| Data Lake Objects (DLOs) | FrcstCustmzAdjustment |
| FrcstCustmzOwnerAdjustment | |
| Period | |
| User | |
| UserRole | |
| Data Model Objects (DMOs) | Business Period |
| Forecast Item Manager Version Amount | |
| Forecast Item Owner Version Amount | |
| User | |
| User Role |
Note To use Data Governance features, grant permissions to the
listed objects according to Grant Access to Data Cloud Objects. If you have more than
one data space, you must grant access to objects in each data space. Object names in non
default data spaces follow the convention of <DataSpace Prefix>_<Object Name>.
Note Data 360 governance features are enabled by default for new orgs.
Review Data Governance Considerations to learn about data
spaces, permission sets, and access policies.
Note Data 360 governance features are enabled by default for new orgs,
but you must create policies to grant data access. Create an Allow All policy if granular
control isn’t needed. In existing orgs, Data 360 includes a day zero Allow All policy out
of the box to preserve access based on current permission sets and data space mappings.
ReviewData Governance Considerations to learn about data
spaces, permission sets, and access policies.
Note Data masking policies and behaviors can be impacted by custom org
configuration, customization, and existing policies. Learn more in Data Governance Considerations.
Note Custom org configurations, customizations, and existing policies can
impact data masking policies and behavior. Learn more in Data Governance Considerations.
For more details, see
.
Did this article solve your issue?
Let us know so we can improve!
