In Blindata, responsibilities play a central role in data governance, enabling users to clearly define ownership and accountability over data assets. Each resource can be associated with responsibilities based on predefined roles. When a user is assigned to a resource, this assignment is recorded in the Stewardship Responsibilities registry, ensuring traceability and historical context.

By assigning responsibilities, organizations can identify technical or business points of contact for specific data assets. Responsibilities can be assigned to individual users or teams, offering flexibility in managing stewardship across different structures.

Responsibilities Registry

Within the Stewardship section, users can access the registry of responsibilities defined on the platform. The table is automatically filtered for the currently logged-in user, making it easy to view personal responsibilities.

The registry can be filtered by:

• User
• Role
• Team
• Resource
• Active/Inactive status

The list of responsibilities can be exported to CSV format, either filtered or complete.

Each responsibility record displays:

• Assignee: the user or team responsible
• Role Name: the role with which the assignee is qualified on the resource
• Resource Type: the kind of resource (e.g., Data Product, Concept, Physical Entity)
• Resource Name: the name of the associated resource
• Description: a brief description of the responsibility, if provided
• Start Date / End Date: the active period of the responsibility
• Actions:
  • Terminate: immediately ends the responsibility; it is no longer active in dashboards but remains visible in the registry
  • Delete: permanently removes the responsibility from the system

How to Assign a Responsibility

Responsibilities can be assigned in two ways:

1. From the Responsibilities Registry, by clicking the “+” icon at the top right.
2. From the detail page of a resource, under the “Responsibilities” tab.

Clicking the "+ Add" button opens a modal window to assign a responsibility to a team or a user.

The assignment modal includes:

• User: the user responsible
• Team: the team responsible
• Description: a summary of the responsibility
• Resource: the associated data resource
• Role: the role assigned
• Start Date: when the responsibility begins

Note: Responsibilities cannot be edited after creation. They can only be terminated or deleted.

Delegating Responsibility Management

Responsibility management can be delegated by assigning appropriate permissions to users, enabling distributed governance within the organization.

To assign a responsibility on a resource, a user must have both:

• The STEWARDSHIP_EDITOR permission, and
• Write access to the specific resource.

Alternatively, users with the STEWARDSHIP_ADMIN permission can assign responsibilities on any resource even without write access to that resource.

This separation allows responsibilities management to be delegated via ACL (Access Control List) configurations. For example, if ACL is enabled on domains:

• A user with the STEWARDSHIP_EDITOR permission
• And a responsibilities that grants write responsibilities on the domain

can manage responsibilities across all resources in that domain even without write access to individual resources. This supports flexible delegation while maintaining access boundaries.

Automatic Assignment of Responsibilities

When a new resource is created, Blindata can automatically assign responsibility to its creator.

If the creator holds a role that includes the type of resource being created, the platform automatically assigns them responsibility for the new resource. This ensures that every new resource has at least one responsible actor from the start.

For example, if a user has a role with operational permissions on Concepts, they will be automatically assigned responsibility when they create a new Concept.