Ability to share request queue with more than one group

[PatrickAd]

I find the sharing functionality of request queues very limiting. We want the ability to specify more than one group that we want to have access to the queue rather than just the one the project is tied to. The current 4 choices for who can add requests to this queue do not fit this criteria and here's why:

Anyone - this is okay if you're the only group using the tool. However, if your tool is at an enterprise level, then the list of request queues are too much.

People with view access to this project - we don't want to give our clients access to our projects. They are the main group submitting requests.

People in this project's company - We have requestors across multiple companies.

People in this project's group - one group is not enough

[KellieGardner]

Could you share it with the 2 groups you want to give access to and then use the "People with view access to this project"?

That's how I typically do it. 

[PatrickAd]

Thank you.

When I try this the user (an external user) is able to see all requests submitted on the project which I don't want them to but they can submit a new request.

[skyehansen · Accepted solution]

we typically recommend routing away from the request queue for this reason. If the request queue project stays empty, anyone can view it. Requests are routed to projects that are controlled by specific working teams based on their needs. Additionally this tactic is more sustainable and insures that the queue project can grow and change over time without messing up any historical requests.