Get started as a platform administrator
As a platform administrator, Ansible Automation Platform helps you enable your users and teams to develop and run automation.
Learn the basic steps to get set up as an administrator for Ansible Automation Platform, including configuring and maintaining the platform for users.
To get started as an administrator, learn to:
- Log in for the first time.
- Configure authentication.
- Manage user access with role-based access control.
Log in for the first time Copy linkLink copied!
Log in to the Ansible Automation Platform as an administrator and enter your subscription information. You can then create user profiles and assign roles.
Procedure Copy linkLink copied!
What to do next Copy linkLink copied!
After your first login, you must add your subscription information to begin using the platform.
Add your subscription Copy linkLink copied!
To add your subscription information, you can either upload your subscription manifest, or use your service account credentials to find the subscription associated with your account.
Before you begin Copy linkLink copied!
To add your subscription by uploading a subscription manifest, you must first:
- Obtain your manifest file. See Obtaining a manifest file for more information.
To add your subscription using your service account credentials, you must first:
- Have created a service account and saved the client ID and client secret.
- Add your service account to the Subscription viewer user group to give it the ability to see your subscriptions. See the "Updates to subscription management" section in the Knowledgebase article Configure Ansible Automation Platform to authenticate through service account credentials for instructions on how to do so.
Procedure Copy linkLink copied!
- To add your subscription by uploading a subscription manifest:
- Drag the file to the field beneath Red Hat subscription manifest or browse for the file on your local machine.
- To add your subscription with your service account credentials:
- Select your subscription and click .
- Check the box indicating that you agree to the End User License Agreement.
- Review your information and click .
If you enter your client ID and client secret but cannot locate your subscription, you might not have the correct permissions set on your service account. For more information and troubleshooting guidance for service accounts, see Configure Ansible Automation Platform to authenticate through service account credentials.
Configure authentication Copy linkLink copied!
After your first login as an administrator, begin configuring authentication for your users. Depending on your organization’s needs and resources, you can either:
- Set up authentication by creating users, teams, and organizations, and then assigning them roles that govern access.
- Use an external source such as GitHub to configure authentication for your system.
The following sections serve as an introduction to authentication in Ansible Automation Platform.
Manage user access with role-based access control Copy linkLink copied!
Role-based access control (RBAC) restricts user access based on the user’s role within the organization they are assigned to in Ansible Automation Platform. The roles in RBAC refer to the levels of access that users have to Ansible Automation Platform components and resources.
Use RBAC to control what users can do with the components of Ansible Automation Platform at a broad or granular level. You can choose whether the user is a system administrator or normal user, and align roles and access permissions with their positions within the organization.
You can define roles with multiple permissions that can then be assigned to resources, teams, and users. The permissions that make up a role govern what the assigned role allows. Permissions are allocated with only the access needed for a user to perform the tasks appropriate for their role.
The following procedures show how to get started with RBAC by creating a team, and a user to assign to the team.
When managing users, teams, and organizations, use the Unified UI or the platform gateway API to ensure real-time synchronization across all platform components, including Event-Driven Ansible controller. If you use the legacy automation controller API, changes can take up to 15 minutes to propagate to Event-Driven Ansible controller, which can result in authentication errors for new users or teams.
Create an organization Copy linkLink copied!
Ansible Automation Platform automatically creates a default organization. If you have a self-support level license, you have only the default organization available and cannot delete it.
Procedure Copy linkLink copied!
Create a team Copy linkLink copied!
Manage teams by creating them, assigning an organization, and adding users or administrators. Team members automatically inherit all assigned roles and permissions. Users must exist in the system before they can be added to a team.
Procedure Copy linkLink copied!
Create a user Copy linkLink copied!
You can create three types of users in Ansible Automation Platform:
About this task Copy linkLink copied!
- Normal user
- Normal users have read and write access limited to the resources (such as inventory, projects, and job templates) for which that user has been granted the appropriate roles and privileges. Normal users are the default type of user when no other User type is specified.
- Ansible Automation Platform Administrator
- An administrator (also known as a Superuser) has full system administration privileges, with full read and write privileges over the entire installation. An administrator is typically responsible for managing all aspects of and delegating responsibilities for day-to-day work to various users.
- Ansible Automation Platform Auditor
- Auditors have read-only capability for all objects within the environment.
Procedure Copy linkLink copied!
What to do next Copy linkLink copied!
If you log in as yourself, and view the details of your user profile, you can manage tokens from your user profile by selecting the Tokens tab. For more information, see Adding a token.