Ui Path Learning ath Licensing Recommended Setup and License Distribution Next, we're going to discuss the relation between the different environments of the automation and the available licensing options. The ultimate goalis to deploy the digital workforce and start the automation journey. However, some steps need to be fulfilled beforehand in order for that goal to be achieved successfully. Firstly, the organizational processes must be modeled as automation workflows during the development phase. Secondly, the functionality of the resulting workflows should be tested in a safe environment before being promoted to the Production one. Only then will they be performed by the entire robotic workforce, and the company will benefit from the automation initiative. We strongly recommend the segregation of the Pre-Production and Production environments How does all that relate to licensing? Well, in the Pre-Production environments, namely the Development and Testing ones, Development and NonProduction Robot licenses are required. The Development Environment is where RPA developers can collaborate on the creation of automation packages and upload them to Orchestrator. They can also download previously created package versions to complete or enhance them.Ui|Path Learning ‘When the development phase ends, the projects need to be tested, to make sure they work as expected. The robots used for that purpose are the NonProduction ones. They execute the automation workflows in the Testing Environment before the promotion to Production. Another benefit of this environment segregation is that developers are prevented from having access to any sensitive information that may exist in the Production environment. Finally, it's time to start the automation itself! In the Production Environment, the Attended and Unattended robots will be working tirelessly to execute the automated processes. Now, for Studio and Attended Robots, there are 2 licensing options - Named User and Concurrent User, while for Unattended Robots, the Concurrent Runtime license is the only option available. We've already explained how these work, so we can move on. Named User and Concurrent User licenses cannot coexist within a single Orchestrator tenant. As a result, the most suitable licensing model needs to be selected out of the two. As stated earlier, all the acquired UiPath Platform licenses can be managed through Orchestrator. For that reason, all the platform licenses must have the same anniversary date. Moreover, an Orchestrator instance can be split into multiple tenants, in order to isolate and secure data. This option is useful for process segregation per department or business unit if the need arises.Ui|Path Learning Host licensing provides fullcontrol of all the licenses belonging to an organization. This option allows for centralized license distribution and management across all the tenants. However, each tenant can also be licensed individually. This covers our Recommended Setup and License Distribution topic.