Security role templates and export & import

[Walter.Koller]

It would be helpful to be able to create and apply templates for user security role definitions in System tab. Additionally to be able to export and import those templates to move from one environment to another.
Being able to export security roles in structure format will allow to run security audits on granted permissions (eg discrepancies between template and individual settings).
This will support us in our multi team environment with 4 roles x 9 teams (and growing).

[ChristopherJank]

under Security / User Role: I wold like to export the User Roles incl. Permissions and in Useers to another instanz of BluePrism

[aaron.diaz]

This would also benefit backup of a system. So if something did go wrong and recovery was needed in the worst case we have another method to use to re-import the configured roles and permissions that may be different then out of the box.

[Walter.Koller]

And we are still and again in need of a template feature for roles, especially when it comes to Studio: group level permissions.

We have created our own type of templates by creating user roles like '00-dev', '00-runtime', ... assign standard functional permission to those roles and then clone them whenever there is the need of another specific role. 
This works well for user role permissions. Although this has to be repeated for all environments separately instead of create one global template and then apply (import) it to all BP instances. 

With permissions on group level in Studio, this also worked more or the less well in BP v6.4 but I was told this was actually a bug and was removed in v6.9.

Why a template feature and/or inheriting of permissions (functional and access) is needed:
We need one RR user role for mostly all of our robots, since often one robot works for one department and must not mix with permission from other departments. This is of course true for automated systems but is also needed in Blue Prism to be able to clearly separate activities, audit them properly and avoid even the possibility of execution beyond department borders. (well... banking policy)

On group level in Studio inheritance is needed as our access rights for robots include one common group/folder and one department group/folder.
Either the new role is for a robot in the same department and they share the same common and department group permissions and cloning the existing user role would solve the definition of new user role.
Or it is a new department with new department group but at least the common group could be copied for a generic RR user role template.

Even we have now a stable set on environments and adding new RR is less frequent, there is still the problem when upgrading to new BP version. Depending on the upgrade plan, either a new BP environment is set up and the existing environment is migrated into it. And all user roles and permissions have to be done again manually
Or the existing BP environment is upgraded but still might be updated manually whenever there was a change in permissions (like new permission were introduced from v6.4 to v6.9). In this case every single user role in user role definition but also in Studio group restrictions, has to be touched.

Unfortunately the user role permission definition window in Studio is lacking any usability in v6.4 and is still lacking in v6.9. I am hoping this was improved in v7.1. At least the list of user roles should be sorted alphabetically

[robert.nicklin]

Hello @Walter.Koller,

Thanks for taking the time to raise an idea.

We do not plan to introduce an import/export function for user roles in BPE. Based on this update, I'm going to mark this idea as Not Planned at this time. Should the votes for this idea increase drastically we can revisit this, or alternatively if any other ideas for the same enhancement exist then votes from this idea can be merged into the alternate.

Regards,

Rob

[robert.nicklin]

Hi @ChristopherJank,

This idea is a duplicate of another idea already in the ideas portal - I've marked this as having a status of Duplicate and will look to merge the ideas shortly.

Regards,

Rob