Segregation/Restrictions of Queues within BP Instance

[KarthikaPalanis]

Process and objects can be restricted from studio via access restrictions between different roles. But on the same note, Queues cannot be restricted between groups/users. Its directly exposed in Control room for all users who have access to the BP instance.

The impact is that, when we have shared environment, there is ask to get the access restricted for Queue for complaint reasons as the item tag can have any unique values between roles. Just because we are unable to do it, it leads to create  a separate BP Database  which in turn leads to additional maintenance, cost and housekeeping etc.,

It would be great if the feature can be introduced to have the restriction in place for queues as well.

Thanks in advance

[umadronadula]

Great idea and it's very helpful.

[EmersonF]

That would definitely help

[AmyTsaousi]

Hi Karthika, thank you so much for sharing your idea. 

We've reviewed your idea and have found that it's a duplicate of another idea which is currently under consideration: https://community.blueprism.com/innovate/ideas/viewidea?IdeationKey=4C095FAE-D484-4B45-922A-4C9D1A5C03B7 
You can currently vote and comment on the idea I've linked as we'll marked this idea as Duplicate which closes off voting and comments.

Thank you so much,
Amy