Roles and Permissions
Last updated
Last updated
There are advanced configuration options that allow you to assign roles to users and groups enabled on the platform for each workspace, as well as for specific form templates. Unlike Users And Groups, which grants or restricts access to the Build application through the Form.Manage role, Authorization profiles provide stricter control over the permissions users have on specific content within this application.
To get started, navigate to the Authorization profiles section from the side menu, where you'll find a list of active profiles. By clicking on the profile name, displayed in blue, you can manage the permissions enabled for it. Each profile can assume one of three possible roles for a workspace, which can be selected by clicking the arrow to the right of the workspace name:
None: Has no permissions, meaning the user cannot view the forms on their RPA Connect portal homepage or work on created instances.
Contributor: The templates from that workspace will be available on their homepage, and they can create new form instances.
Manager: In addition to having Contributor permissions, they can also view all form instances submitted by profiles with access to the template.
By clicking the arrow to the left of the workspace name, you can expand the list of form templates contained within it and also assign specific roles to each of them. In addition to the three options mentioned earlier, there is the Inherit option, which means inheriting the permission assigned to the workspace without changes.
The New button in the upper-right corner allows you to create a new profile, with three possible types: User/Group, ApiKey, and Client App. We will focus on the first two.
Building on what was covered in the previous section, let's start with users and groups. Click on New > User/Group and add a name and, optionally, a description for the profile. Select the User type and enter the email address registered in Users And Groups. Try assigning different types of profiles to workspaces and the forms within them. The changes will be reflected on the RPA Connect portal homepage and in the form instance submission section, where users will see more or less information depending on the level of authorization granted.
Click Save changes to finish.
To add a group, follow the same steps as above, but select the Group type instead of User. Unlike workspaces, in this case, you do not need to enter an ID; the application will display a dropdown menu where you can select the desired group from those already registered.
The ApiKey allows authentication from robots, automation, or code that interacts with the forms. You can assign the same roles to this type of profile as you would to a user or group.
To create a new profile, click on New > ApiKey, enter a name and, optionally, a description, and click Add. The system will generate a unique key that you must copy and save.
Keep in mind that when using the RPA Connect API, you will need to use this ApiKey for authentication.
