Explore Data Space Functionality

Learning Objectives

After completing this unit, you’ll be able to:

Identify when to use data spaces.
Explain key features of data spaces.
Implement data spaces.

As of October 14, 2025, Data Cloud has been rebranded to Data 360. During this transition, you may see references to Data Cloud in our application and documentation. While the name is new, the functionality and content remains unchanged.

Data Spaces in Data 360

Data 360 allows you to create a data space to organize data to fit your business needs. You can segregate your data, metadata, and processes by categories, such as brand, region, or department. Once segregated, users can be granted access to a data space.

A diagram that shows the Data Space Architecture with data sources feeding data into various data spaces.

When you or others view the data, you see only the data assigned to that data space. After you enable a data space, Data 360 applications run user and system data services in the context of the data space. This means a data space can impact all types of work downstream, including calculated insights, segmentations, and activation.

Use Cases

Let’s explore two scenarios where using a data space makes sense.

You’re using a single Data 360 instance and need the flexibility of running multiple regions, departments, or brands.
Your business requires your users to see and work on data only in the context of their region or brand.

Now, where does using a data space not make sense?

You have data residency requirements and must ensure that data doesn’t cross regional boundaries. Data spaces don't solve data residency needs.
Your primary goal is cross-brand unification and targeting.

Key Benefits and Best Practices

Let’s review what the data space functionality enables you to do.

Segregate your data, metadata, and processes for these brands, regions, and departments with full autonomy.
Manage user access control to designated data spaces through permission sets.

Implement Data Space

If you’re a new customer, an initial empty data space is created in your Data 360 instance and you can start using it. You can’t delete the default data space but you can change its display name.

Each data space is provisioned with a permission set. When your account is assigned to the data space permission set, you can create object mapping, identity resolution rulesets, insights, data actions, segments, and activation targets in the data space. Users with a Data Cloud Architect permission set and a System Administrator profile can create, edit, and delete a data space. A Data Cloud architect can add data to a data space. Refer to the permission sets documentation linked in the Resources section below for the most current information on Data 360 standard permission sets.

Build Your Data Strategy with Data Spaces

Now that you have the basic information about data spaces, start thinking about how you can use this feature in your org. Whether you use it to organize data or to segregate it, you can better govern and maintain a data strategy using data spaces.

Time Estimate

Topics

Looking for Help?

Data Cloud Resources