Skip to main content

About workspace permissions

You can see the list of actions you can perform depending on the workspace permissions assigned to you.
Permissions Actions
Author
  • Create, edit, or delete tasks and plans
  • Manage the configuration of tasks and plans

    For example, you can configure the Artifact and Parameters steps when creating or editing a task.

  • View and delete artifacts
  • Manage tags
Execute
  • Run tasks and plans
  • Manage the schedule and run configuration including the engine, log level, execution timeout

    For example, you can configure the Processing and Schedule steps when creating or editing a task.

  • Access engines allocated to the workspace and all shared engines in the environment
View View the task and plan details pages, run history and logs
Availability-noteDeprecated
Manage
  • View and delete artifacts
  • Create, edit, and delete connections and resources

    For example, you can configure the Connections and Resources steps when creating or editing a task.

    Information noteImportant: For more information on how to migrate the Manage workspace permission, see Migrating the Manage workspace permission.
Publish Publish artifacts
Use engines Restrict the use of an engine.

By default, Talend Remote Engines can be used in all the workspaces of an environment. You can restrict the use of an engine to selected accounts by allocating it to a specific workspace and then grant the Execute or the Use engines permission on this workspace to these accounts.

  • Users with the individual permission Engines - Use can only have the workspace permission Use engines. This workspace permission is the combination of the Execute and View permissions. For more information, see Predefined roles for Talend Management Console.
  • Users with the Tasks and Plans - Edit or the Connections & Resources - Edit user permission cannot be assigned the Use Engines workspace permission.

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 – please let us know!