Is it possible to have a request queue where the requestor can only view the requests they submit?

I've asked for this for a long time now. It's a breach of confidentiality for everyone to see everything.

I searched Innovation Lab and didn't see anything specifically asking for the ability to lock down the filter for Requests > Submitted to be only 'My Requests,' but I really support this. Perhaps this can be combined with these two?

Idea: Custom Filters Submitted Requests (workfront.com)

Idea: Ability to adjust view on the Submitted Requests page (workfront.com)

Hi Victoria & Elena,

There is a workaround that will accomplish what you are looking for. I can't recall where I learned it (someone here) but create a 'landing project' for your requests. If you search landing project you'll be able to find something I'm sure.

Here's how it's setup:

Requestors access the queue.

Requests shows up as submitted on their end.

Request is routed to show up on a landing project that the requestor does not have access to. All requests 'sit' here and therefore only people with view access to that project can see them.

For us, our request queue 'project' is named 'Request Agency Assistance'.

Once submitted, it routes to a project called '-Agency Marketing'*

*This was named a 'friendly' name since the request confirmation email that a requestor gets will say 'your request has been added to Agency Marketing'

Requestors can only see the request they submitted at that point.

Let me know if you have any questions and good luck!

Thank you for raising the questions and for the additional comments and suggestions.

Christina’s suggestion is a valid way to setup things, especially if it also makes sense from your workflow perspective, for example where you’d rather have requests from the same topic sit in their own projects.

I would also like to highlight the ways you can control who gets access to the submitted requests. It is possible to restrict access to the submitted requests. It is more cumbersome for already created requests, but you can setup things properly moving forward to limit the access. I've recorded a video to show you the steps. In short, you will have to

• remove the existing access from the requests (this should be done carefully not to remove the access for the users that do need it)
• remove the automatic rules that share the access to the request
• remove the access from the project to prevent inherited access to the requests/issues in that project. This will of course work if your setting of “Who can add requests to this queue?” is not set to “People with view access to the project”

Let me know if this is helpful or if you have additional questions/comments.