Explicit duty segregation - credentials, queues

[Martynas]

From BP 6.4 you can partially segregate teams - separate folders for objects, processes, resources.
Unfortunately some critical parts are still common. It would be great to have a way for teams:

• To manage/see their own credentials
• To manage/see their own work queues

[Manoj_kumarNunn]

Hi,

It will be good to have MTE environment implemented for Process dependencies like, Work queues, Environment variables, credentials etc..,
Currently it is applicable on Studio for groups and on Control room for differentiate runtime resources.

Thanks,
Manoj

[John__Carter]

That'll come Manoj. The original ambition was to be able to completely divide the environment but as the work went on, the guys decide to stop at processes, objects and resources in order to get the first incarnation of MTE released. As you might imagine, handling the dependencies between assets like queues, env vars, env locks, schedules, fonts, etc etc gets increasingly complicated.

[Manoj_kumarNunn]

Hi John,
Thank you. any idea on which release these changes will be incorporated.
Thanks,
Manon

[John__Carter]

I don't know Manoj, I suspect the team are waiting for real-world feedback on the efficacy of the current MTE functionality, and I guess as yet not that many enterprises are using it in anger. So rather than commit to the considerable effort of taking MTE further, they'll want to know what the market wants.

[Walter.Koller]

Access rights management for credentials should be presented in tree view with the structure based on group definition in Studio tab and Resource Management in System tab. Additional group view for security roles would be appreciated in System tab \ Security \ User Roles as well as the Access rights window (both for Access rights management and for group Access rights in Studio tab). 
Currently, user roles in Access rights management are not even ordered, neither for Credentials, nor for groups in Studio tab.

This should enable to grant credential usage to single processes and whole groups of processes (eg all processes of department Accounting when defined as group in Studio).

[astrid.stollberger]

We have a pretty big RPA developer community for which our central operations team needs to manage the credentials as we cannot grant everyone the "Manage Credentials" permissions. This is because with "Manage Credentials" permission everyone would be able to change the Password and/or update the "Access Rights" settings for any credential even without knowing the current Password - which is pretty bad.

So we are trying to automate the credential management but here again, it's apparently not possible without UI automation of Blue Prism itself as there is no other way to set the "Access Rights" for a given credential than via the UI.

It would be great if there would be either 
a) a simple API which would allow creation of credentials (including Access Rights settings) in an automated fashion
b) [preferred option] a better access management / authorization check for credential management, so that we could just grant everyone the "manage credentials" permission and if they have the current password they can update/delete the credential if they want to; if not, they will not be able to edit the credential. Only System Admins should probably still be able to edit any credential without having to provide the current password.

[MelanieGiuliani]

Thank you for your idea! This is very similar to an existing idea, which can be found here: https://community.blueprism.com/ideas/ideas/viewidea?IdeationKey=4c095fae-d484-4b45-922a-4c9d1a5c03b7. I've marked this idea as duplicate in order to keep all comments, votes, and lifecycle tracking in one place. Please direct all further conversation and votes to the existing idea.

[MelanieGiuliani]

Thank you for your idea! This is very similar to an existing idea, which can be found here: https://community.blueprism.com/ideas/ideas/viewidea?IdeationKey=4c095fae-d484-4b45-922a-4c9d1a5c03b7. I've marked this idea as duplicate in order to keep all comments, votes, and lifecycle tracking in one place. Please direct all further conversation and votes to the existing idea.

[ChristianLinden]

this is a showstopper for us trying to implement full teams segregation

[MelanieGiuliani]

Hi Martynas,

Thanks so much for submitting your idea! We are moving it into the Under Consideration status while we route the idea through our internal review process. 

We will update you as your idea moves along the lifecycle.

Thank you!

Melanie