Currently, there are 3 access roles for the organizations:

  1. Guest
  2. Integrator
  3. Admin

Each role is limited to the given organisation only. The same user in the platform can have different roles in different organisations, however, there are operations which are independent of organisational structure:

  • Configure own SSH Key (this is independent of organisational structure)
  • Configure own profile information including the name, e-mail address and the password.
  • Access own API Key connected with the current organisation
  • Permanently delete his/her own account.

Guest Role

Guest role is perfectly suited for giving an introduction to the project to a third party without showing any critical details of it. This user can not do anything but examine the project. Here are the operations that Guest can and can't-do on the platform.

Can

  • See the integration flows of all the members of the same organisation
  • Examine the structure of any integration flow
  • Examine the execution details of all the flows (logs, data count and errors)
  • Access the list of current and pending members of the organisation with their access roles.
  • See the component development teams, component repository details - if invited by another member with Admin access rights
  • See only the list of security credentials for each component.
  • See list of lookup tables

Can’t

These are limitations of the guest user:

  • Start/Stop integration flows
  • Modify or delete integration flows
  • Invite a new member to the organisation
  • Change the role of any member of the organisation
  • Invite a member to development team
  • Add, modify or delete any repository or repository record
  • Add, modify or delete any security credential
  • Add, modify or delete any lookup table

Integrator Role

Integrator role is pretty much self-explanatory. It gives the user an ability to design and deliver integration projects. Here are the details what this role holder can and can't-do.

Can

  • All operations of Guest +
  • Start/Stop/Modify and Delete all integration flows in the organisation. The modified flows change the ownership to the initiator.
  • Examine the execution details of all the flows (logs, data count and errors)
  • Access the list of current and pending members of the organisation with their access roles.
  • See and Modify the component development teams, component repository details - if invited by another member with Admin access rights
  • Add, Modify and Delete any security credentials in the organisation
  • Add, Modify and Delete any lookup table

Can’t

  • Invite new organisation member or change the access role of any member
  • Create development team
  • Invite a member into an existing development team
  • Modify environment variables of any repository within the organisational unit
  • Delete a repository

Admin Role

Admin role holder can perform all the operations of the Integrator and more. This user role is perfectly suited for setting up the project in the first instance. Here are the details what this role can and can't-do.

Can

  • All operation of the Integrator +
  • Invite a new member into organisation
  • Change the access role of any member but himself/herself
  • Can create development teams
  • Invite new members into a team to which he/she are part of
  • Modify environment variables of any repository within the organisational unit
  • Delete a repository of which they are member of

Can’t

  • Change their own role in the organisation - other Admin would need to do it
  • Be member of every development team unless invited by other Admin