Kapplets User Roles
When a Kapplet is ready for use, a Kapplet user or a group of users can obtain access privileges to the Kapplet through a specialized workspace. A group of users can work only with a set of Kapplets defined by the administrator. Kapplet users keep a list of the installed Kapplets in their workspace.
As a Kapplets user, you can only access the repository within the projects that you are eligible to access. For example, when you log in to Kapplets as a User, you can only run Kapplets for robots belonging to projects for which you have the access rights.
If a Kapplet contains at least one robot belonging to a project that you do not have access rights for, it is shown with a warning icon and a tooltip stating that this Kapplet is disabled. The same scenario applies if the robots have been removed from the Management Console. In other words, to run a Kapplet, you must have the rights (at least the Kapplet User role) for all the projects containing these robots and the robots must exist in the Management Console repository.
The same rules also apply to schedules and templates.
Kapplets are built and maintained by users depending on their roles and privileges, which are assigned and changed by the global administrator on the Kapplets side. For example, if you create a user in the Management Console with no privileges, the Kapplet Administrator can change these privileges, overwriting the initial settings.
-
User: Runs Kapplets.
-
Developer: Creates Kapplets and Templates, runs Kapplets.
-
Administrator: Creates Kapplets, Templates, and Workspaces; runs Kapplets and assigns privileges.
To create Templates, a Kapplet user (Developer or Administrator) must be granted the Kapplet Administrator role in Management Console for the projects that contain the robots required for the Templates.
Equivalents of the Management Console roles in Kapplets
Management Console group role |
Kapplets group privilege |
---|---|
Kapplet User |
User |
Developer |
Developer |
Kapplet Administrator |
Developer |
Project Administrator |
Administrator |
RPA Administrator |
Administrator |
These privileges can be of two types: local privileges and global privileges:
-
Global privileges are managed at the system-wide level and can be assigned to a group of users, where each user inherits the privilege, or to a certain user.
-
Local privileges are assigned only to the user groups of a certain workspace, users inherit these privileges from the user group .
If you are assigned the Kapplet User role in the Management Console, in the Kapplets interface, you can only run Kapplets, while to edit Kapplets, you must be assigned the Kapplet Administrator role. These two roles limit the access to the Management Console repository used in Kapplets: robots, types, and more.
Transfer of Kapplets roles
All Management Console roles related to Kapplets that were assigned to users in a previous product release can be transferred to the new Kapplets by importing a Management Console backup to the new Kapplets. The roles from the backup are converted into their equivalents in the new Kapplets.
Also, as Kapplets is a standalone application, if a user is assigned a role related to Kapplets in the Management Console, it is not automatically transferred when the user logs in to the Kapplets. The new role or any role change must be explicitly confirmed by the global administrator, that is, assigned to the user on the Kofax RPA side.
Restore Kapplets from Management Console backup
Apart from creating new Kapplets, Classic Kapplets can also be restored with the Management Console backup with the option Merge.
The users are also moved to Kofax RPA Kapplets within their user groups. These user groups and users get no privileges, until these privileges are assigned by the global administrator.
Objects from Management Console backup are moved to the Kofax RPA Kapplets the following way:
Management Console backup objects |
Kofax RPA Kapplets objects |
---|---|
Project |
Workspace |
Master Kapplet |
Template |
Installed Kapplet |
Kapplet marked as "favorite" |