Configure permissions, connect your Git provider, and set up content sources before users can create and build execution environments.

The setup process depends on your automation portal deployment model:

• OpenShift Operator: You configure SCM integration, authentication providers, wizard templates, and content discovery declaratively in the AutomationPortal custom resource manifest.
• OpenShift Helm chart or RHEL appliance: You configure individual integration sections by updating your Helm values file or the app-config.production.yaml configuration file, then apply the configuration changes.

Complete the following setup workflow for execution environment builder:

1. Configure collection discovery sources for your Git repositories and private automation hub.
2. Connect to GitHub — configure a GitHub App or personal access token (PAT) for content discovery, and an OAuth App for saving definitions.
3. Connect to GitLab — configure a PAT for content discovery, an OAuth App for saving definitions, and CI/CD variables for automated builds.
4. Configure wizard templates — host templates in an internal repository if operating in air-gapped environments, and enable cloud or network automation templates.
5. Create standardized templates for your teams.
6. Apply configuration changes to your cluster or appliance.
7. Synchronize content sources.
8. Configure permissions — grant execution environment builder access to non-admin users.