[Aperçu] Gestion de la visibilité des locataires et des services

Vue d'ensemble (Overview)

Customers can control the visibility of the services and tenants that are available to their users, based on their permissions and the service status.

Tenant and service visibility can be managed for the following services:

• Orchestrator

• Actions (via Orchestrator)

• Integration Service (via Orchestrator)

• Processes (via Orchestrator)

• Data Service

• Document Understanding

• Apps

• Automation Ops

• Task Mining

• Test Manager

• Insights

Main user scenarios

Scenario 1: Service visibility in the left navigation based on permissions

Scenario 2: Tenant visibility at service level based on service permissions

Scenario 3: Tenant visibility at service level based on service availability

Limites connues

Feature not visible as a UI item

Managing tenant and service visibility is not displayed as a UI item that can be toggled on or off. The feature can be triggered in the existing services menu (changing a user's permission in Orchestrator) or based on settings you make in the existing Automation Cloud (enabling / Disabling Services).

Remarque :

The presented screenshots serve as a guidance setup.

Managing visibility for Integration Service, Actions and Processes is done via Orchestrator permissions

You can control Integration Service, Actions and Processes visibility via Orchestrator permissions, meaning that if a user has any permission in Orchestrator, they can see and use Integration Service / Actions / Processes.

Remarque :

There is no granular permission at Orchestrator level that controls if a user has access to Integration Service / Actions / Processes or not.

Workaround: Use the Advanced settings from the tenant level to hide the service for non admin users.

Setup to test tenant and service visibility

Remarque :

The following steps serve as a setup example.

1. Create two tenants named Production and Testing.

   

2. Create a group named UAT Users.

3. In the Production tenant, ensure that the UAT Users group does not have permissions in any service.

   As an example, for Document Understanding, navigate to Manage Access and check that the UAT Users group does not have a role assigned.

   

4. In the Testing tenant, associate the UAT Users group with permissions for the services you want the users to test on (Orchestrator, Document Understanding, Insights, etc.).

   As an example, for Document Understanding, navigate to Manage Access and assign a role to the UAT Users group.

   

Check setup for tenant and service visibility

Remarque :

The following steps and scenarios serve as examples on how to check the setup for tenant and service visibility.

1. Login with a user from the UAT Users group.

2. Check what the user sees in the left navigation for Testing and Production tenant.

3. Check what the user sees in the tenant picker.

Scenario 1: Service visibility in the left navigation based on permissions

1. Follow the Setup to test tenant and service trimming steps.

2. Log in as a user from the UAT Users group.

3. Check what the user sees in the left navigation for the Testing and Production tenants.

Remarque :

On the homepage, the user only sees the Testing tenant, not the Production tenant, because the users from the UAT Users group only have access to services from the Testing tenant. When the Testing tenant is selected, the user sees the services they have access to in the left navigation.

Remarque :

If the user has permissions to view only one tenant, then that specific tenant name does not show up on the homepage.

Scenario 2: Tenant visibility at service level based on service permissions

1. Follow the Setup to test tenant and service trimming steps.

2. Log in as a user from the UAT Users group and select one of the enabled services from the left navigation. For example, Document Understanding.

3. Check what the user sees in the tenant picker.

The user does not see the tenant picker anymore because they only have permissions to view enabled services in the Testing tenant, and not the Production tenant.

Scenario 3: Tenant visibility at service level based on service availability

1. Follow the Setup to test tenant and service trimming steps.

2. Log in as an org admin with full rights.

3. Disable or enable the service.

4. Log in as a user from the UAT Users group.

   Notice that you can only see the enabled services in the left navigation or for which you have permissions in that particular tenant.

5. Check what the user sees in the tenant picker.

FAQ

How long will it take for the tenant visibility to take effect after the role assignment changes in the service?

It can take up to 10 mins for direct role assignment changes and up to 1 hour for group membership, based permissions changes.

Will this feature work also with UiPath Assistant?

Yes, but only if you have installed version 23.4 or higher of UiPath Assistant.

Where can I see this feature in the user interface?

The enhanced access control for tenants and tervices is not visible as a UI item that can be toggled on or off. The feature is triggered based on settings you make in the existing Automation Cloud (enabling / Disabling Services) or in the existing services menu (changing a user's permission in Orchestrator).

Would enabling this feature affect my data?

The feature works with the visibility of the data and features of the users. It does not affect or can cause any data loss.

Remarque :

For managing the visibility of organization-wide services, refer to the UI Customization settings documentation.