- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Saving the connection strings
- Step 2: Creating your organizations in Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting

Automation Suite on OpenShift installation guide
Step 2: Creating your organizations in Automation Suite
You must manually create your organizations in Automation Suite. The organization name must comply with the following Regex format: '^(?!.*$)[a-zA-Z][A-Za-z0-9]+$'.
The organization name must start with an uppercase or lowercase letter and must contain at least one character after the initial letter. Then, the name can include any combination of alphanumeric characters or underscores. Note, however, that the organization name must not end with an underscore.
For example, valid organization names include Username, user_name1, or User123. Make sure to avoid invalid formats such as _username (does not start with a letter), username_(ends with an underscore), user name (contains a space), or user@name (contains an invalid character).
You do not have to manually create the tenant as the migration tool automatically performs this operation for you. The organization and tenant names do not have to be identical. While the organization name is customizable, the Automation Suite tenant name is the same as the standalone Orchestrator tenant name.