"Run Typeahead As"

[William--]

I could really use the gang's support in voting for this Idea Exchange post . Body of the request is: We love the Typeahead fields and how quickly they've evolved to enable so many use cases. One challenge we have is, we want any user in our organization to select a value from a list of certain projects in a request form. But, they cannot enter these project names in the Typeahead because they lack View access to the projects in question. The only way to enable those projects to be entered is to grant View access of these restricted projects to the entire org. We broadly and regularly share with the org that these projects exist (using Run Report As feature), but don't want to grant access to the actual projects. I understand why Typeaheads work this way, doing their part to mask the existence of private projects, and I support that. But, similar to the many use cases in which one would "Run a Report As," we would want to " Run a Typeahead As" and allow users to view and enter project names, even when they don't have View access to the projects themselves. Unless this is already planned on the roadmap, @Josh Hardman ? Workaround suggestions welcome... I've tried making a single task visible system-wide in these projects, but that still did not suffice to make the projects select-able in the request forms. William English

[joshh79242137]

I'm curious about which elements of a project you are trying to protect? It seems that you want people to know these projects exist. You want them to be able to see certain parts of them in reports with "Run as". You want them to be able to search for them by name in the typeahead fields. So what pieces do you want to keep from their view? Josh Hardman Product Manager, Workfront

[William--]

We want to keep all of it out of view of those users who aren't assigned to the projects (outside of the fact that it exists.) We often share status reports for these projects just so the org as a whole has a basic understanding of the volume of work, but don't allow users to look at the specific issues, documents, or update stream contained in the projects being reference in the Typeahead. The closest comparison in terms of concept or use case would be published request queues that are visible to everyone. The queues are visible to all users in the Requests landing page menu option, but (most of the time), the requests getting logged are immediately routed to private projects which are not universally accessible. Basically, we want people to reference these projects in the custom form, but don't want them to see the "sausage making." William English T-Mobile