To use Data 360 Data Governance features for Sales Workspace, you need to grant access to the impacted objects according to an access policy.
Required Editions
Select from either attribute-based access control (ABAC) or role-based access control (RBAC) for more granular control over 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 in Enterprise, Unlimited, and Agentforce 1 Sales editions with the Sales Foundation add-on. |
Associated Data 360 Objects
| Object TYpe | Name |
|---|---|
| Data Lake Objects (DLOs) | Lead |
| Opportunity | |
| OpportunityHistory | |
| Forecasting Fact | |
| Forecasting Item | |
| Business Period | |
| User | |
| Account | |
| Data Model Objects (DMOs) | Opportunity |
| Opportunity History | |
| Lead | |
| Forecasting Fact | |
| Forecasting Item | |
| Business Period | |
| User | |
| Account |
Note To use Data Governance features, grant permissions to the listed objects according
to Assign Data Access. If you have more than one data space,
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, 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 Custom org configurations,
customizations, and existing policies can impact data masking policies and behavior. Learn more
in Data Governance Considerations.
For more details, see