ElectroNeek roles and permissions system makes it possible to differentiate the existing platform components from each other for specific users. That being said, it is possible to manage access to the desired products based on what kind of work your Team members do.
Roles are divided into Team roles and product-specific roles. Team roles apply to a Team in general while product-specific roles define the level of permissions within a single product.
Here is the guide that explains how setting up Team members and their roles works. Step 3. Team onboarding
When a user joins the Team, he or she can have one of the following roles: Owner, Admin and Member. Here are the details about these roles.
Owner is in charge of a Team. Features:
Can invite anybody to the Team.
Can modify roles for anybody.
- Can grant permissions for other users to use any product.
Can revoke the permissions to use the a product.
Can exclude a member from the Team.
Can not be deleted by anyone in the Team.
The next role is Admin. This role is typically used to grant persons permissions to manage the specific products. It is mostly similar to Owner, but and Admin is unable to remove the Owner from the Team.
Member is the last and the most common role. They do not have any specific rights regarding the Team. Members can be assigned to any products.
We have just reviewed the roles related to a Team in general. Now let us review the roles according to the specific products.
There are no multiple roles. This means that any persons who are eligible to use this program are able to do any kind of work in Studio including building and running bots.
There are no multiple roles. Anyone can use it freely when running attended bots. For unattended bots, users need to have the corresponding rights and permissions.
There are two roles in Orchestrator:
Analyst. You can learn more about roles in Orchestrator in this article.