Authorization Data Model
The Authorization Data Model provides a high-level overview of the core building blocks of the CIVITAS/CORE's authorization system.
Core Concepts
| Concept | German | Description | Example |
|---|---|---|---|
| Platform | Plattform | Represents the entire TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. as an authorization scope | City of Berlin |
| User | User | Individual within a TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. | Alice Smith |
| Group | Gruppe | Groups of Users within a TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. | Data Analytics Unit |
| Permission | Berechtigung | Smallest atomic authorization | Read Data |
| Role | Rolle | Group of permissions | Data Analyst |
| Scope | Geltungsbereich | Specific area or element for which access can be controlled | DataPool "Traffic Data Domain" |
| Assignment | Zuordnung | Mapping defining who gets what where | Alice has Role "Data Architect" in DataPool "Traffic Data Domain" |
| DataSet | Datensatz | Protected data product | Traffic Statistics 2026 |
| DataSource | Datenquelle | Source of Data related to a specific connector. | Traffic Statistics 2026 (CSV) |
| DataStructure | Datenstruktur | Schema or data model describing the structure of data. | Traffic Measurement (CSV) |
| DataPool | Datenpool | Logical container for datasets | Traffic Data Domain |
A Tenant (Isolated Environment)
A TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. represents a fully isolated environment for a specific organization. All Users, Roles, and access rules exist securely within their TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.. What happens in one TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. does not affect any other.
Each TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. owns its elements — Users, Roles, 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., etc. — as integral components (technically modeled as composition). In the diagram, this relationship is reflected by the TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. being defined as a property within related entities.
In the authorization model, access that applies to the entire TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. is represented by the Platform Scope.
The User and Groups (Who?)
A User represents an individual who accesses the system.
Each User strictly belongs to one TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform..
In order to assign a Role to a User, he/she must be assigned to a Group.
Permission and Role (With What?)
A Permission is the smallest atomic unit of authorization, like a single key, e.g., "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." or "delete 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.".
A Role is a collection of Permissions, comparable to a keyring. It groups all Permissions required for a particular job or task.
Managing Roles rather than individual Permissions makes administration much more efficient.
Scope (For What?)
A Scope defines an area or element within the Platform for which access can be controlled.
CIVITAS/CORE supports the following Scopes:
- Platform: representing the entire TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.
- Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space.: a logical grouping of 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., such as "All Traffic Data"
- 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.: a specific data product that needs protection, such as "Traffic Statistics 2026"
- 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.: a specific source of data
- Data structureData structureA versioned data-related element that defines the schema and organization of data. It specifies how data is structured and interpreted within the Platform.: a specific schema or data model
Scopes allow access to be defined at different levels, from the entire Platform down to individual data-related elements.
Assignment (The Link Between Them)
At the heart of the model lies the Assignment, which acts as a central mapping or rulebook defining access control.
Each assignment explicitly answers:
Who (
Group) gets which Role (Role) for what (Scope)?
Examples of different Scope levels
The Group
Data Analytics Unitis assigned the RoleData Architectfor 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.Traffic Statistics 2026. The resulting Permissions apply only to this 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..
The Group
Data Analytics Unitis assigned the RoleData Architectfor thePlatform. The resulting Permissions apply to all data-related elements across the Platform.
This flexible scoping mechanism allows very fine-grained or Platform-wide access control.
Concepts in Detail
Permissions
Permissions have an attribute category that is used to group them. This is especially useful for system-level permissions.
There are two types of permissions:
-
System Permissions
- Apply to system-administrative operations.
- Cannot be modified by Users.
- Some are instance-level (e.g., creating a new tenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.), others tenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.-level.
- Also apply on client level.
-
Data Permissions
- Enable access 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., Data structuresData structureA versioned data-related element that defines the schema and organization of data. It specifies how data is structured and interpreted within the Platform., 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..
- Access can be defined to the definition of these enitities (metadata level) or the content of these entities (payload level)
- Cannot be modified by Users.
- Include standard data permissions.
- Also available on client level.
Roles
Roles are grouped according to the type of permissions they contain:
- System Roles: contain system permissions
- Data Roles: contain data permissions
- A Role contains one or multiple permissions.
- Can be created by Users.
- Are assigned at Data structuresData structureA versioned data-related element that defines the schema and organization of data. It specifies how data is structured and interpreted within the Platform., 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., 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., Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space., or platform level.
Default Roles
The system comes with default Roles based on predefined permissions:
- Purpose: ensure the system is ready to start and reduce effort in Role creation.
- Users can use them but are not required to.
- Default Roles are not modifiable.
- Default Roles have the attribute
readonlyset totrue.
Users
- A User can receive multiple System and Data Roles through their Group memberships.
Groups
- All Users in a Group implicitly inherit the Group’s System or Data Roles.
- A Group can have one or multiple System and Data Roles.
- Groups are the only mean to assign a Role (and thus Permission) to a User.
Binary Assignment: Permissions to Roles
Overview
Permissions are assigned to Roles to enable platform access. The CIVITAS/CORE platform defines its own permission model that is mapped to the respective permissions of each application within the platform (e.g. Superset, Grafana).
Usually, data permissions are predefined in the respective applications, e.g. FROST comes with a predefined set of data permissions. The CIVITAS/CORE platform will transparently map its own permissions model to these predefined application permissions.
Standard Role Definitions
| Name | Role type | Main Objectives | Rights | Typical Role in Administration |
|---|---|---|---|---|
| Platform Admin | System | Configuration of tenantsTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.. System monitoring with the aim to identify logical, stability-related or resource-related problems on the platform. Working closely with the operations staff of the K8 cluster to ensure that the platform is stable and has enough resources. | Management rights for the configuration of tenantsTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. and basic system parameters. Monitoring permissions of all platform system information. | IT personnel |
| TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. Admin | System | User, Role and Permissions management. Configuration of tenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.-wide system parameters. | TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.-wide permissions to manage Users, Roles and Permissions as well as tenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. parameters. | IT personnel or technical specialist in cross-domain department (e.g. geoinformation or smart city department) |
| Data Architect | Data | Definition of guidance on the structuring and administration of data on the tenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.. Definition of commonly used data models and metadata. Administration of Data poolsData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space.. Administration of 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., Data structuresData structureA versioned data-related element that defines the schema and organization of data. It specifies how data is structured and interpreted within the Platform., transformation pipelines, metadata and APIs. Works closely with all other Roles on the TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.. | Management rights for all aspects of data ingestion, data processing, data storage and data output. | Technical or data specialist in cross-domain department (e.g. geoinformation or smart city department) |
| Data Consumer | Data | Consumption of data. | Authenticated or non-authenticated User on the platform. If authenticated, User can access all data he/she has permissions to in his/her Roles. If not authenticated, User can access open data and public functions. | Everybody |
| Data Steward | Data | Management of domain specific data concepts within a Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space.. Application of data and metadata standards models created by the Data Architect. Creation, update and deletion of 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.. | Responsibility for the life-cycle of domain specific data in a Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space.. | Department employee, data / domain specialist |
| Data Owner | Data | Definition of data guidelines and cooperation in data governance definition. Release authorization of new 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.. | Business responsibility for one or several domains. | Chief Officer or Department Head |
| Data Gatekeeper | Data | Definition of data governance models and processes on the tenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform.. Administration of data governance models. Release authorization of 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 are affected by privacy concerns. | Responsibility for data protection and data governance | Chief Data Officer (CDO), Data protection officer |
Standard System Role Permissions
System Permissions control administrative operations on the Platform. They are grouped by administrative area.
TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. Administration
| Object | Operations |
|---|---|
| Assignment | Create, Read, Delete |
| Group | Create, Read, Update, Delete |
| Permission | Read |
| Role | Create, Read, Update, Delete |
| User | Create, Read, Update, Delete |
Standard Data Role Permissions
- 🟢 Data Architect
- 🟣 Data Consumer
- 🟠 Data Steward
- 🔵 Data Owner
- 🟤 Data Gatekeeper
| Permissions / Objects | READ | CREATE | UPDATE | DELETE | RELEASE |
|---|---|---|---|---|---|
| DataSet | 🔵🟠🟢🟣🟤 | 🔵🟠🟢 | 🔵🟠🟢 | 🔵🟠🟢 | 🔵🟤 |
| ↳ Payload | 🔵🟠🟣🟤 | 🔵🟠 | 🔵🟠 | 🔵🟠 | - |
| DataSource | 🔵🟠🟢🟤 | 🔵🟠🟢 | 🔵🟠🟢 | 🔵🟠🟢 | 🔵🟤 |
| DataStructure | 🔵🟠🟢🟤 | 🔵🟠🟢 | 🔵🟠🟢 | 🔵🟠🟢 | 🔵🟤 |
| DataPool | 🔵🟠🟢🟣🟤 | 🟢 | 🔵🟠🟢 | 🟢 | - |
Available Scopes for Data-related elements
| Permissions / Objects | READ | CREATE | UPDATE | DELETE | RELEASE |
|---|---|---|---|---|---|
| DataSet | Platform, DataPool, DataSet | Platform, DataPool | Platform, DataPool, DataSet | Platform, DataPool, DataSet | Platform, DataPool, DataSet |
| DataSource | Platform, DataSource | Platform | Platform, DataSource | Platform, DataSource | Platform, DataSource |
| DataStructure | Platform, DataStructure | Platform | Platform, DataStructure | Platform, DataStructure | Platform, DataStructure |
| DataPool | Platform, DataPool | Platform | Platform, DataPool | Platform, DataPool | Platform, DataPool |
Binary Assignment: System Roles and Groups
System Roles are assigned to Groups to enable platform access. This is a binary assignment, i.e. a Group is directly assigned a System Role. The Platform Scope is implicit, as System Roles always apply Platform-wide.
- A System Role consists of multiple permissions.
- It can be created by Users.
- Some are provided by the system by default.
- Control administrative and platform-level functions.
Ternary Assignment: Data Roles and Groups Across Levels
Data Roles can be assigned to Groups on multiple levels. Important: This is a ternary assignment, i.e. a Group is assigned a Data Role in respect to 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., Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space., Data structureData structureA versioned data-related element that defines the schema and organization of data. It specifies how data is structured and interpreted within the Platform., 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., or platform level.
(Data) Platform level
- Roles can be assigned at the platform level.
- Enables efficient and global management of Roles across the entire platform.
- Role-Group Assignments defined at Platform level apply to all data-related elements across the Platform.
Data pool level
- Role-Group Assignments defined at the Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space. level can be inherited by 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. within the Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space..
- This allows common access rules to be managed centrally while 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. can have additional Assignments where needed.
Dataset level
- Role-Group Assignments can be defined directly for 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..
- If 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. belongs to a Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space., it can also inherit Role-Group Assignments from the Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space..
- Inherited Assignments can be extended by additional Assignments defined specifically for 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..
- 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. does not have to belong to a Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). Formerly called Data space..
Data source level
- Role-Group Assignments can be defined directly for 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..
- Access to 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 required to use it in a Pipeline within 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..
Data structure level
- Role-Group Assignments can be defined directly for a Data structureData structureA versioned data-related element that defines the schema and organization of data. It specifies how data is structured and interpreted within the Platform..
- Access to a Data structureData structureA versioned data-related element that defines the schema and organization of data. It specifies how data is structured and interpreted within the Platform. is required to use it within other data-related elements, such as 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. or 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..
- Access defined for a Data structureData structureA versioned data-related element that defines the schema and organization of data. It specifies how data is structured and interpreted within the Platform. applies to all of its versions.
This allows differentiated role assignment depending on topics, departments, and data responsibilities.