How to limit visibility of request types within a queue in a project

[Melanie.Johnson]

We have a Project which is being utilized by several of our Team Members as they need to handle the request based on the Business Unit that reports the issue. Within this project we have 2 request types related to HR that we would only like certain users to be able to view in the queues.  Currently these appear in the Open ticket and several other queues which the Service Desk uses.  Is there a way to restrict these 2 request types (Employee Onboarding and Employee Offboarding) so that only the Product Managers and Service Desk employees can see them? Right now we have Business Analysist in the queue who we do not want them to see these Request types.  One way we were thinking is if we possibly put these employees in a group and set up security somehow for that group?

Thanks in advance for any thoughts on this.

[Walter Buggenhout]

While @Shikha Verma's response about issue security schemes to apply security on issues in the same project is 100% accurate, it may be a better (and more scalable) approach to create a separate JSM project for your HR-requests alongside the other one.

People will still be able to access all service requests they have access to from a single, central portal. But the backend queues would be separate for teams with their own specific set of services.

It is easier to restrict access at a project level than issue by issue, and you have a considerably smaller risk of issues accidentally ending up in the wrong permission level that way. 

Hope this helps!

[Shikha Verma]

Hi, @Melanie_Johnson, You can achieve this by using Issue Security Schemes.
You can refer to this link for more detailed information/steps. Create security levels for issues. 
Also, you can refer to this link Add or Remove restrictions on request types.
Hope this will help!

[Melanie.Johnson]

Thank you!  We will play around with the security level schemes. When I look at the Add or remove restrictions on a request type, it looks like that is only for who can create the issue and  we are looking for who within the project can view the issue once created.

[Shikha Verma]

@Melanie.Johnson Yes, the second link is for those who can create the issue.
But the first link you can refer to sets security levels.