Share Pipeline with Entitlement

This section aims at describing the behaviour of a shared pipeline when used with an entitlement.

Entitlement is a crucial component of data governance, acting as the control mechanism that defines and enforces what actions specific users or groups can perform on a data pipeline. It ensures data security, compliance, and operational integrity by providing granular control over access.

The Share Pipeline action allows you to grant specific entitlements to other users. This means you can control what actions they can perform on your pipelines, such as viewing, editing, or executing them.

Here's how entitlement restricts or permits users with various permissions for a data pipeline:

• View Permission (Read Access):

  • Permits: Users with "View" permission can see the data pipeline's configuration, metadata, status, and execution logs. They can understand its structure, what data it processes, and its current state. This is essential for monitoring, auditing, and understanding data flow without altering it.

  • Restrictions: They cannot make any changes to the pipeline, execute it, or delete it. This prevents accidental modifications or unauthorized operations.

• Edit Permission (Write Access):

  • Permits: Users with "Edit" permission can modify the data pipeline's configuration, transformational logic, data sources, and destinations. They can update existing steps, add new ones, or reconfigure parameters. This allows for pipeline development, maintenance, and optimization.

  • Restrictions: While they can modify the pipeline, they may not necessarily have the right to execute it. This separation ensures that a pipeline is fully reviewed and approved before being run in a production environment. They also typically cannot delete the pipeline unless explicitly granted a higher permission.

• Execute Permission (Run Access):

  • Permits: Users with "Execute" permission can initiate a run of the data pipeline. This means they can trigger the data processing workflow, either manually or as part of a scheduled job. This is vital for operations and data delivery teams.

  • Restrictions: They generally cannot view or edit the pipeline's configuration unless they also possess the respective "View" or "Edit" permissions. This allows operational teams to run pipelines without the ability to alter their logic, preventing unauthorized changes to data transformations.

Please note: Users with all three permissions (View, Edit, and Execute) have complete operational control over the shared pipeline.

By combining these permissions, administrators can establish a robust access control model, assigning the right level of access to the right users based on their roles and responsibilities within the organization. This safeguards sensitive data, maintains data integrity, and supports efficient, secure data operations.

Watch this illustration to see how changing entitlements directly impacts a user's access permissions.