Skip to main content Skip to complementary content

Built-in roles and workflows

Talend Data Stewardship comes with predefined roles and workflows.

Roles are used to manage user authorization on tasks and functionalities and they are assigned in Talend Administration Center .


Campaign owners can be technical or business users:
  • Technical users are in charge of populating campaigns with actual data by using Talend Jobs and output governed data to target systems.
  • Business users are in charge of creating campaigns and data models. They organize, supervise and monitor the tasks they assign to data stewards. Campaign owners can participate as data stewards.
Campaign operators are technical users with limited access to Talend Cloud Data Stewardship interface. Their role is to integrate data into Talend Cloud Data Stewardship via Talend Studio, Talend Cloud Pipeline Designer or Talend APIs. They can:
  • List the campaigns.
  • Read the data models.
  • Read, create and edit some tasks.
Data stewards are business users in charge of resolving tasks. They can:
  • Classify data by assigning a label chosen among a predefined list of arbitration choices.
  • Curate one or several fields of the task record by fixing invalid values or by providing missing values for example.
  • Merge several potential duplicate records into one single record.

Data stewards do not need to have particular technical skills.

Rule managers are technical users in charge of managing What is a data quality rule?.

Rule viewers are business users only allowed to view data quality rules.


Workflows define the steps necessary to resolve the tasks in a campaign. A workflow is composed of states, linked to each other by transitions.

  • Two-step workflow: Defines one initial state and one final state where the newly created tasks are picked up by given stewards, handled and then marked as resolved.
  • Multi-step approval workflow: Defines one initial state, one or more validation states and one final state. The newly created tasks are picked up by given stewards, handled and then forwarded to other stewards in charge of approving the task resolution before they are marked as resolved.

    The multiple approval steps are useful when it is necessary to double check data by stewards who have different rights when visualizing tasks or have different expertise.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!