Datapools
Role: Data Architect, Data Owner, Data Steward
Goal: Organize DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. into Datapools, control access on a higher level, and manage shared ownership and governance.
Required Permissions: read Datapool, create Datapool, update Datapool, delete Datapool; read DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions., create DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions., update DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
What is a Datapool?
Datapools help organize related DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. within the Platform. They provide a shared context for ownership, access management, and Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. availability across multiple DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions..
Assigning a DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. to a Datapool is optional, but recommended.
What you will achieve
After completing this guide, you will have:
- Create and manage Datapools
- Assign DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. to Datapools
- Configure access on Datapool level
- Restrict Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. availability for Datapools
- Organize DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. within a shared governance context
Common use cases for Datapools
Use Datapools when:
- multiple DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. belong together
- ownership is shared
- permissions should be managed consistently
- DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. represent one organisational unit
Avoid creating Datapools for individual DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. only.
Create and edit a Datapool
- Go to Datapools
- Click Create Datapool
- Define Name, Description and Owner in the 1st tab Base information
- Hit Save
The Datapool exists now but contains no DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions..

Add Datasets to a Datapool
Assign an existing Dataset
- Go to DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
- Open a specific DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
- Select a Datapool in the 1st section Base information
- Hit Save

Moving a DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. to another Datapool may affect access permissions. Review the permissions of the target Datapool before making changes.
Create a new Dataset within a Datapool
- Open the Datapool
- Navigate to the DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. tab
- Select Create DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
- Complete the DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. creation process
The selected Datapool is automatically assigned to the new DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions..

Configure access on Datapool level
In the Access tab, you define which Groups can access and manage the Datapool itself.
→ Depending on the assigned Role, the same assignment can also grant access to all contained DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.. This allows access to multiple DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. to be managed through a single Group and Role assignment.
Choose an access strategy
| Strategy | Example | Result | Recommended |
|---|---|---|---|
| Centralized access management | Assign a Group to the Data Steward Role on Datapool level | Group members can manage the Datapool and all contained DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. through a single assignment | ✅ yes |
| Combined access management | Assign a large Group to the Data Consumer Role on Datapool level and manage additional Roles on individual DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. | All users can discover and read DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions., while editing permissions remain controlled on individual DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. | ✅ yes |
| Organizational grouping only | Assign a custom Datapool-specific Role without DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. permissions on Datapool level | The Datapool is used for organization only. DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. permissions are managed independently | ⚠️ Advanced use case |
Assign Groups and Roles on Datapool level
- Open the Access tab
- Add a Group
- Assign a Role to the Group
- Repeat these steps to add more Groups and Roles
- Hit Save

For a detailed explanation of permission inheritance and authorization concepts, see → Authorisation.
Review Datasets and Data sources
The Datapool detail view provides an overview of the DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. and Data sourcesData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. associated with the Datapool.
Tab DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.: View all DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. assigned to the Datapool.
Tab Data sourcesData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network.: View all Data sourcesData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. that have been released for the Datapool and are available for use by its DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions..
Restrict Data sources for Datapools
Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. availability for Datapools is configured in the Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. detail view.
→ By releasing a Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. for one or more Datapools, you control in which DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. the Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. can be selected during pipeline configuration. A Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. is only available in DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. that belong to a Datapool for which the Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. has been released.
For example, a Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. containing information about critical infrastructure may only be intended for specific organisational units and therefore be released only for selected Datapools.
Data sources can be made available to:
- all Datapools
- selected Datapools
- no Datapools
DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. without a Datapool assignment can only be targeted indirectly through the All Datapools option. Assigning DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. to a Datapool is therefore recommended.
Restricting Data source availability allows you to:
- control which Data sourcesData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. can be used within specific organisational areas
- reduce complexity for DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. creators by showing only relevant Data sourcesData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network.
- support governance and compliance requirements
Configure Data source availability
- Open the Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. detail view
- Navigate to the Datapools tab
Either: You keep the default setting "Approve for all Datapools" (DE: Für alle Datenpools freigegeben) enabled. This makes the data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. available to DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. in all Datapools, as well as to DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. without a Datapool assignment.
Or: You disable the setting "Approve for all Datapools" (DE: Für alle Datenpools freigegeben). In this case, you can specify the individual Datapools for which this Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. should be released. If you disable the default setting without adding any specific Datapools, the data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. cannot be used in any DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions..
- Hit Save

Delete a Datapool
→ A Datapool can only be deleted when no DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. are assigned to it. Before deleting a Datapool, open each contained DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. and decide:
- assign it to another Datapool (recommended)
- remove its Datapool assignment
To delete a Datapool
- Open Datapools
- Locate the Datapool in the table
- Select Delete from the Actions column
- Confirm the deletion
The Datapool is removed from the Platform.
Best Practices
Recommended
- ✅ Organize Datapools according to organisational responsibilities
- ✅ Use Datapools to simplify permission management
- ✅ Reuse Datapools for related DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
Avoid
- ❌ Creating a Datapool for every DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
- ❌ Duplicating permission assignments unnecessarily
Related Articles
→ Core Concepts → Authorisation → Connect external data → Release Data