- Introduction
- Product lifecycle
- Licensing
- Delivery options
- UiPath Platform
- Platform guidelines for partners
- Localization support
- Compatibility matrix
- Attended vs. Unattended automation
- Activities overview
- UiPath documentation
- Troubleshooting
Platform guidelines for partners
This page is intended for UiPath partners who manage deployments on UiPath® Automation Suite or UiPath Automation CloudTM.
When designing and configuring your UiPath platform, it is essential that you set it up in a way that allows for proper data sovereignty, access control, and security controls for you and your clients.
This page describes the overall platform structure across our various delivery options.
Refer to Delivery options, for more information on the delivery options.
The UiPath automation platforms, whether in cloud or on-premises, have a particular hierarchical structure. Let's look at each, starting from the highest level, to the lowest.
The host level is only available in UiPath Automation Suite and in standalone installations of UiPath Orchestrator.
The host is the control plane for a single deployment which allows you to define global settings that are inherited the lower levels - organizations.
An organization typically corresponds to a client's company and it serves as the dedicated instance of the UiPath platform. Each organization is distinct and has its own organization settings, security settings, licenses, and user directory.
Within an organization, you can configure multiple tenants, each with its own set of services and all of these services trust the organization directory as the source of truth for accounts, groups, and external applications.
This shared organization directory model requires that each of your clients have their own organization.
Cloud hosting region: In UiPath Automation Cloud, an organization can be deployed to a hosting region of choice. This allows clients to choose the region in which the shared organization data resides. Refer to Data Residency and About organizations in the Automation Cloud guide for more information.
A tenant represents a container within an organization that governs UiPath services. Services within a tenant can seamlessly integrate with each other while services across different tenants generally do not.
In Automation Cloud, a tenant can be deployed to a region of choice. This allows your clients to choose which region to isolate all of the data utilized and generated by the services in a tenant.
Refer to About tenants in the Automation Cloud guide for more information.
To onboard a client, we recommend that you follow this process:
- Decide where to manage the client: on-premises with Automation Suite or in the cloud with Automation Cloud.
-
Create a new organization for the client.
As a partner, you can use the same UiPath account to create multiple organizations, in which case you are the system administrator (on-premises) or organization administrator (Automation Cloud) within the multiple organizations you create.
-
Configure the organization security settings according to the needs of your client.
For example:
- You can set up Automation Ops to enforce an upgrade policy for your client's employees.
- You can enforce session policies.
- Develop a plan on how to best leverage tenants and folders according to your client's needs.
- Develop a plan on how to deploy the Platform services to meet the customer's needs.
-
Develop a plan to onboard users at scale:
- Ask the client if they have an identity provider, and if they do configure Azure AD or SAML directory integration. Otherwise, be prepared to create accounts for all of their users.
- Configure permissions for groups so it is easier to manage access.
