Create and manage users and groups for private automation hub through its web UI and configure access permissions for users by using groups.
Enterprises can use private automation hub to manage and control the lifecycle of their Ansible content. They can host Ansible Content Collections and automation execution environments on their private automation hub and provide controlled access to their users.
Different user groups can be content creators, operators, or domain experts, who each need a different level of access to the content. For example, the content creators group needs permission to write and modify the automation code, whereas the operator group needs read-only access to run an automation job.
Private automation hub provides a simple but efficient way of managing user access to the content. User access is based on managing permissions to system objects. The system objects are users, groups, namespaces, and repositories.
To manage content and access to content in private automation hub, you can create groups and assign object permissions to those groups. Then you can assign users to these groups, so that each user in a group has the permissions assigned to that group. Managing permissions for groups might be easier than managing permissions for individual users.
You can create and assign permissions to a group in private automation hub that provide access to specified features in the system for members of that group..
Use the following procedure to add a new group to private automation hub:
Log in to your private automation hub using credentials for the admin user configured during installation.
Navigate to → and then click .
Enter a valid name and click to create the group.
Click .
Click in the field for each permission type and select permissions that appear in the list.
Click when finished assigning permissions.
You can add permissions when you create groups or edit an existing group to add or remove permissions.
The following table lists the types of private automation hub permissions.
| Object | Permissions | Permission description |
|---|---|---|
| , , , and | Create, modify, or delete namespaces, and upload Ansible Content Collections to them. | |
| Delete Ansible Content Collections. | ||
Move Ansible Content Collections between repositories, using the Approval feature to certify an Ansible Content Collection and move it from the staging repository to the published repository, or to reject it and move it from the staging repository to the rejected repository. | ||
| , , , and | Manage user configuration and access in private automation hub. | |
| , , , and | Manage group configuration and access in private automation hub. | |
| and | Configure or view configured remote repositories of Ansible Content Collections that can be synchronized to the private automation hub, under → . | |
| Change permissions on the container repository. | ||
| Change information on containers. | ||
| Modify image tags on containers. | ||
| Upload new containers. | ||
| Delete a container repository. | ||
| Push an image to an existing container. | ||
| , , and | Add, change, or delete remote registries in private automation hub. | |
| , , and | Manage tasks under in private automation hub. |
The private automation hub installation process creates the default admin user. This user is assigned all permissions in the system.
You can create users in private automation hub and add them to groups. Use the following procedure to add a new user to private automation hub:
Log in to your private automation hub using credentials for the admin user or as a user who has permission to manage users.
Navigate to → and then click .
Enter a valid , , , , and .
Assign the user to a group by clicking the field and selecting from the list of groups.
Keep the as .
Click .
Super users are assigned all system permissions regardless of what groups they are in.
You can create different groups in private automation hub and assign different permissions based on their role. For example, you can create one group for system administrators responsible for governing internal Ansible Content Collections, configuring user access, and repository management. You can create another group for content curators responsible for organizing and uploading internally developed content to private automation hub.
Suppose in your organization you need to create a new group in private automation hub to manage automation content. The group manages the internally developed Automation Content Collections and the automation execution environments in private automation hub.
Use the following procedure to add a new group to private automation hub and assign necessary permissions:
Log in to private automation hub using credentials for the admin user.
Navigate to → and then click .
Enter app_team in the field and click to create the group.
Click .
For permissions, select , , , and .
For permission, select .
For permission, select , , , , .
Click .
Next, create a new user andrew as a member of app_team group.
Log in to your private automation hub using credentials for the admin user or as a user who has permission to manage users.
Navigate to → and then click .
Enter andrew as the and redhat123 as the .
Assign the user to group app_team by clicking in the field and selecting from the list of groups.
Keep the as .
Click .
Verify that user andrew can manage Ansible Content Collections.
Log in to private automation hub as the user andrew.
Navigate to → .
Click .
Enter a name for the namespace and select app_team as .
Confirm that the user can upload Ansible Content Collections in the namespace.
Verify that user andrew can manage automation execution environments.
Log in to private automation hub as the user andrew.
Navigate to → .
Private automation hub provides content creators a single source of truth to collaborate and publish their automation content within their organizations. To efficiently manage access to your automation content, you can create groups with the right permissions and add users into those groups. This approach is simple compared to assigning permissions to individual users.