Assigning RBAC to the Automation controller
During the previous chapters, organizations, teams, and users were created. However, unless the users are admins, they have limited access inside the Automation controller.
Roles in the Automation controller follow the basic rules of RBAC . This means that each role has a set of permissions for what it is allowed to do. These roles fall into categories of allowing objects to be viewed, edited, and executed with the controller. In addition, the roles themselves are attached to organizations, teams, and users. Teams and users are interchangeable; it’s just that teams are a collection of users.
In addition, there is a hierarchy of roles. The hierarchy of roles follows inheritance. Some roles inherit permissions from other roles. The way to think of this is that a read role can only read, a user role can read and use an object, and an admin role can edit, use, and read an object.
The roles available in the Automation controller...
