You are here:
Data Space Aware Objects and Features
User access to data space-aware objects and features is controlled by setting the object permissions and feature permissions in the user's permission sets. Not all objects and features are data space aware.
These objects are data space aware.
- Data lake objects (DLOs)
- Data model objects (DMOs)
- Calculated insight objects (CIOs)
- Data graphs
These Data Cloud features are data space aware.
- Data shares
- Data graphs
- Identity resolution
- Calculated insights
- Einstein Studio AI models
- Data actions
- Segmentation
- Activation
- Data semantic search
- Search Index
If you have View All Records and Modify All Records permissions on the primary object for a feature, you can view the object metadata regardless of the data space scope access.
System-Level Permissions and Data Space Access
System-level permissions such as View All Records (VAR) and Modify All Records (MAR) don't automatically associate a user with a Data Space. However, users who have these permissions can query data-space-aware objects according to the permissions granted by those system-level permissions. Data Space assignments continue to control access to Data Space-scoped features and administrative operations.
To access Data Space-scoped features and resources, users must be explicitly assigned through Data Cloud Data Space Management. Users with system-level permissions such as VAR or MAR may still be able to query data-space-aware objects based on their granted permissions.
This behavior ensures that Data Space access control remains enforced in compliance-sensitive and multi-tenant environments.
Billing Considerations for Data Space-Aware Features
For billing purposes, all records in a source object are counted even if a downstream process uses a filtered version of the object associated with a specific data space. This is because the data space-specific version of the object is a virtual view of its source object. Queries to a data space-specific object return a filtered view of the source object’s data that is created from all records stored in the object.
Suppose a data lake object (DLO) with 100 records is associated with two different data spaces. In one data space, the filtered view of the DLO contains 75 records. In the second data space, the filtered view of the DLO contains 50 records. However, the number of records counted for billing purposes is 100 records.
Suppose a data lake object (DLO) that contains 50 records is created within a specific data space. It isn’t associated with any other data spaces. The number of records counted for billing purposes is 50.
