DataChain Roles

Summary

  • Roles allow managing access and permissions in a structured and hierarchical way

  • Different scopes exist for roles (Organizational roles, Module roles, Project roles, etc …​)

  • A user’s roles can be direct (assigned to them directly) and/or inherited from one or more groups

  • Roles are always cumulative (additive).

Roles in DataChain

The DataChain platform relies on a highly structured access and permission management architecture, implemented through a robust and hierarchical system combining roles, permissions, and basic rights.
This system is a fundamental pillar of DataChain, ensuring the security, integrity, and operational efficiency of the entire DataChain ecosystem.
It allows different Administrators to precisely orchestrate who can access which resources, datasets, and functionalities, while defining the specific actions each user is authorized to perform on fine-grained resources such as datasets.

Definition of roles

Each role within DataChain is designed to meet specific needs and distinct levels of responsibility.
Roles are designed to adapt to different levels of granularity and responsibility, allowing for precise allocation of permissions across different scopes.

Roles are always additive: access, permissions, and rights accumulate, whether they are direct or inherited.

Organization roles

These roles define permissions at the organization level.

  • The Organization Administrator is responsible for managing users and resources specific to their organization

  • The User is a member of this Organization, which allows them to log in to the DataChain Platform if their account is active

Module role

These roles define permissions at the level of a specific module.

  • The administrator manages global permissions of the users who are members of the module

  • The creator can create top-level elements (Project)

  • The user can work within the instance depending on the Project roles assigned to them

Project role

These roles define permissions at the level of a specific project.

  • The Project Administrator manages the general settings of a project, project members, and the basic rights templates of each member

  • The Project User can work within the Project depending on the global permissions and the basic rights assigned to them