- Getting Started
- Demo apps
- How To
- Notifications
- Using VB Expressions
- Designing your App
- Designing your App with Autopilot
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Value
- Rule: Start Process
- Rule: Reset Values
- Rule: Upload File to Storage Bucket
- Rule: Download File From Storage Bucket
- Rule: Create Entity Record
- Rule: Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Rule: Trigger workflow
- Rule: Submit Action
- Leveraging RPA in your App
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Leveraging Media in your app
- Leveraging Actions in your app
- Leveraging Connections in your apps
- Web apps in Studio Web
- Application Lifecycle Management (ALM)
- UiPath® First-Party Apps
- Basic Troubleshooting Guide
Permission Management
Roles at the tenant and folder level are managed in Orchestrator.
Roles at the app level are managed in UiPath® Apps.
To allow multiple users in your organization to run an app, you need to deploy the app to an Orchestrator folder, then assign the Everyone default group to the specific folder.
Apps are always published to an Orchestrator tenant, similarly to processes.
To manage folder-level permissions for apps, first you need to deploy those apps to an Orchestrator folder.
For more information on managing permissions for apps at folder level, check the Apps section from the Orchestrator guide.
Apps are always published to an Orchestrator tenant, similarly to processes.
For more information on managing permissions for apps at the tenant level, check the Apps section from the Orchestrator guide.
You can control the visibility of the services and tenants that are available to your users, based on their permissions. To learn more about this feature, visit Managing tenant and service visibility.
An organization admin can assign Apps users the following organization-level roles:
-
App Creator - grants Create permissions on Apps.
-
Apps Administrator - grants Read and Create permissions on Apps, and Update permissions on Owners and Permissions.
App Creator role
The App Creator role allows users to create or collaborate on apps. Users with this role can:
-
See and update all the apps they have created (they are owners).
-
See and update all the apps that have been shared with them (they are co-authors).
Members of Everyone and Administrators default groups are automatically assigned the App Creator role. For other default or custom groups, explicit assignment of the App Creator role is necessary.
Apps Administrator role
The Apps Administrator role allows users to manage apps extensively. Users with this role can:
-
Create apps.
-
See all the apps in the organization, both created by them and by other users.
-
Update their own apps and apps shared with them.
-
Change the owner of any app in the organization.
-
Manage the access and roles of apps users.
Members of the Administrators default group are automatically assigned the App Administrator role. For other default or custom groups, explicit assignment of the App Administrator role is necessary.
The Apps Administrator role overrides the App Creator role.
Roles comparison
To grasp the capabilities of each Apps role at a glance, refer to the following table:
Operations |
App Creator |
App Administrator |
---|---|---|
Create, view, update, share, or delete own apps |
Yes |
Yes |
View and update shared apps |
Yes |
Yes |
View unshared apps (of other users) |
No |
Yes |
Update or delete unshared apps (of other users) |
No |
No |
Delete shared apps |
No |
No |
Change the owner of an app |
No |
Yes |
Manage access for other users |
No |
Yes |
Users with the Apps Administrator role can access the Manage Access page. Only organization admins can assign Apps roles.
To assign roles to users:
Users with the Apps Administrator role can change the owner of an app.
Transferring app ownership uses the following scenario:
-
User A initially owns the app.
-
The Apps Administrator switches ownership to User B.
-
As a result, User B becomes the owner, while User A assumes a co-author role.
-
Now, the Apps Administrator transfers ownership to User C.
-
Consequently, User C becomes the owner, and User B joins User A in the co-authors list.
-
Moving forward, the Apps Administrator reverts ownership to User A.
-
User A is removed from the co-authors list and regains ownership. Meanwhile, User C joins the co-authors list alongside User B.
To change the owner of an app:
-
Navigate to the the Build tab.
-
On the card of the desired app, click More Options.
-
Select Change owner. The Assign a new owner wizard opens.
-
In the Search users field, type the name or the email of the new owner, then select it.
-
A pop-up message asks for confirmation. To proceed, click Confirm. Otherwise, click Cancel.
-
Click Assign.
As an app owner or a co-author, to see the list of previous owners:
-
Open the app.
-
Go to App settings, and switch to the Manage access tab. The list displays all users with the co-author role for the current app.
At app-level, you can invite collaborators and grant them the Co-Author role, which allows previewing and editing the selected app.
To run an app, first you need to deploy it to an Orchestrator folder.
- Navigate to the app homescreen by clicking on the gear icon at the top of the right-hand panel.
- Click on the Manage access tab.
- Click on the Assign role button.
-
Type in the user's name in the Search users and groups textbox.
- If the user/group is not shown, they may not be part of the organization, see Adding a user to an organization.
-
Set role to Co-Author (can edit and run).
Adding groups to Apps may take up to 60 minutes to apply.
Alternatively, group members can log out and log in again to see the apps that were assigned to them.