Organize users into teams and explore the access provided by different team roles.
Outcomes
Organize users into teams.
Assign different roles to team members.
As the student user on the workstation machine, use the lab command to prepare your system for this exercise.
This command ensures that automation controller is installed.
[student@workstation ~]$ lab start org-team
Procedure 2.2. Instructions
Create a new team called Developers.
Navigate to https://controller.lab.example.com and log in as the admin user with redhat as the password.
Navigate to → and then click .
Create the team using the following information:
| Field | Value |
|---|---|
Developers
| |
Dev Team
| |
Click to create the new team.
Create the daniel user.
Navigate to → and then click .
Create the new user with the following information:
| Field | Value |
|---|---|
Daniel
| |
George
| |
daniel@lab.example.com
| |
daniel
| |
redhat123
| |
redhat123
| |
The user type is set to Normal User rather than System Administrator. The daniel user will be an administrator of the Developers team, but the user will not be assigned administrative capabilities on the entire automation controller instance.
Click to create the new user.
Assign the daniel user the Admin role on the Developers team.
Navigate to → and then click the link for the team.
Click the tab and then click .
Click and then click .
Select and then click .
Select and then click to assign the role.
Create the donnie user.
Navigate to → and then click .
Create the new user with the following information:
| Field | Value |
|---|---|
Donnie
| |
Jameson
| |
donnie@lab.example.com
| |
donnie
| |
redhat123
| |
redhat123
| |
Click to create the new user.
Assign the donnie user the Read role on the Developers team.
Navigate to → and then click the link for the team.
Click the tab and then click .
Click and then click .
Select and then click .
Select and then click to assign the role.
Create the david user and associate the user with the Developers team. Associating the user adds the Member role for the team.
Navigate to → and then click .
Create the new user with the following information:
| Field | Value |
|---|---|
David
| |
Jackobs
| |
david@lab.example.com
| |
david
| |
redhat123
| |
redhat123
| |
Click to create the new user.
On the page for the david user, click the tab and then click .
Select and then click to assign the Member role.
Click → to exit the automation controller web UI.
Verify the permissions for the daniel user.
Log in to the automation controller web UI as daniel with redhat123 as the password.
Navigate to → and then click the link for the team.
Notice that the button is available, indicating that the daniel user can make changes to the Developers team.
Click the tab.
Notice that the button is available and that each existing role assignment for members of the Developers team contains an , indicating that the role assignment can be removed. The daniel user can manage permissions for the Developers team. Having the Admin role additionally allows the daniel user to inherit permissions assigned to the Developers team.
Click → to exit the automation controller web UI.
Verify the permissions for the donnie user.
Log in to the automation controller web UI as donnie with redhat123 as the password.
Navigate to → and then click the link for the team.
Click the tab.
Notice that the button is not available and that each existing role assignment does not contain an , indicating that the role assignment cannot be removed. The donnie user can view information about the Developers team, but the user cannot make changes to it. Additionally, by only having the Read role, the donnie user does not inherit permissions assigned to the Developers team.
Click → to exit the automation controller web UI.
Verify the permissions for the david user.
Log in to the automation controller web UI as david with redhat123 as the password.
Navigate to → and then click the link for the team.
Click the tab.
Notice that the button is not available and that each existing role assignment does not contain an , indicating that the role assignment cannot be removed. Like the donnie user, the david user can view information about the Developers team, but the user cannot make changes to it. Unlike the donnie user, having the Member role allows the david user to inherit permissions assigned to the Developers team.
Click → to exit the automation controller web UI.