Available roles
Each role corresponds to a specific business profile. For the detailed per-screen permissions, see the permission matrix.
Viewer
Views traces and configurations. Can replay executions on the Development and Other environments.
The Viewer has read access to the whole platform (workflows, triggers, dictionaries, credentials, traces) on the Development and Other environments. They can replay executions to analyze a behavior, but cannot create or modify anything. They have no access to Production data.
Ideal for: an external developer, a tester, a collaborator in the UAT phase.
Builder
Creates and edits workflows, folders and dictionaries. Can test but not deploy to Production.
The Builder has all creation and editing capabilities on the Development and Other environments. They can create workflows, triggers, dictionaries, credentials, and test them. They cannot deploy to Production nor delete structural resources (triggers, workflows, dictionaries).
Ideal for: an integration developer, an integrator in charge of workflow building.
Advanced Builder
All the Builder capabilities, plus Production deployment. Can also manage users and assign roles.
The Advanced Builder can do everything the Builder does, and additionally can deploy to Production, delete resources, edit users and assign roles. They have no access to company management itself (user creation, environments).
Ideal for: a technical lead or integration referent responsible for production rollout.
Exploitation
Read access to everything. Operates traces and dictionaries in Production only.
The Exploitation role is designed for operational teams: they can monitor and act on Production (replay traces, edit dictionary values) without access to workflow building nor the Development and Other environments. Their write scope is strictly limited to Production.
Ideal for: a support or ops team that supervises production workflows without intervening in their development.
Company Owner
Full control over their company or companies: users, rights, deployments, dictionaries, environments.
The Company Owner has all rights on the companies assigned to them. They manage users, assign roles, create and delete environments, and have access to all environments including Production.
Roles are cumulative: you can combine several roles for the same user (e.g. Viewer + Exploitation for global read including Production, or Builder + Exploitation to build outside Production and supervise Production). See Introduction — How it works.
Ideal for: the technical manager or project leader in charge of one or more Ecosystem companies.
Which role for which need?
| Need | Recommended role(s) |
|---|---|
| View and replay only (Development and other env.) | Viewer |
| Build and test workflows | Builder |
| Deploy to Production, delete resources, manage roles | Advanced Builder |
| Monitor and act on Production without touching workflows | Exploitation |
| Global read + Production ops | Viewer + Exploitation |
| Building outside Production + Production ops | Builder + Exploitation |
| Administer the company (users, environments) | Company Owner |