I’m building an app that requires users to sign up/register for an account before being granted access to the app. I know I can send them an invite and have them create a UiPath cloud account, however, when assigning them access to the app, they can only have one role which is App Creator which essentially allows any user to not only create a new app but be able to edit the app they have access to and delete any content they want! This is a true disaster. I haven’t found any way to limit this for them to only run the app and disable editing. The user demo I created is only assigned to the Everyone Group. Is there an alternative way for that? If there is, the other question will come as to how will I be able to distinguish each runtime user? Thanks.
However, when I come to assign the role, I can only assign the user per tenant level and not per folder level. As you can see in the below screenshot, the role is not being found.
Are you not trying to assign tenant cross permissions that is permissions of another tenant to another. Else you can Create separate Orchestrator tenants: If you need to enforce different access levels for different groups of users, you can create separate tenants in UiPath Orchestrator. Each tenant can represent a specific user group or app access level.
Due to new changes, pushing apps is now like publishing process packages to a tenant feed. So, if we want to give any user permission to view only without editing, we need to add the user first to the tenant. In the Manage Access tab, I created a new role called ‘Apps Role (Read Only)’ which only has the View checked. Then, in the Folders tab, I created a new folder called ‘Public Apps’ and then I assigned the new user and gave him the new role which I created. Next, I went to the ‘Public Apps’ folder and clicked on Automations then Apps. From there I deployed the new app which I published and I finally got the public URL link with the option to embed as an iframe. This could have easily be done if they showed us a small tour about the new changes rather than take us on a rollercoaster ride of trying and guessing.
Important: Managing access inside the app itself now only grants a user full access to edit and run the app if given which is called (co-author) with role as App Creator.
Hope this can help someone looking for the same resolution. Cheers