Grant project access, but limit tasks users can see | Adobe Higher Education
Skip to main content
Level 9
March 29, 2021
Pregunta

Grant project access, but limit tasks users can see

  • March 29, 2021
  • 4 respuestas
  • 837 visualizaciones

Hi WF Community,

Does anyone know if it's possible to grant a user access to a project, but only allow them to see certain tasks when viewing a project?

I thought maybe I could just remove sharing access on the tasks I don't want the user to see, but this doesn't work because that user is included in the tasks inherited permission group from project sharing, and if I remove that, other users won't be able to see that task.

I was going to remove sharing for that user at the project level, and only add them at the task level, but this then impacts a project dashboard we have for users where they can see projects they are included on.

Anyhow, curious if there's a path forward on this?

Thanks.

Nick

Este tema ha sido cerrado para respuestas.

4 respuestas

Doug_Den_Hoed__AtAppStore
Community Advisor
Community Advisor
March 29, 2021

Hi Nick,

One approach I've recently adopted is to create reviewer licensed "Audience" users (e.g. First Name = "Audience:", Last Name = "Investors"), assign those users to only the Tasks that they are entitled to see, create a Task filter (e.g. "Audience: Investors") that then only returns such tasks, use that on a report, and even do a Run As/Share of that report to those who need only see the certain tasks.

Regards,

Doug

NickVa7Autor
Level 9
April 1, 2021

Thanks for this idea, Doug. I will keep it in my tray of potential solutions when discussing with stakeholders.

AlisonW
Level 5
April 14, 2021

We have done this on a few occasions. Our process was to create the project, then disable inherited permissions, then create the tasks. Each task must then also have inherited permissions disabled to ensure someone doesn't accidentally get access. Lastly, the desired people are shared to the appropriate tasks. As you can see it is a process, and this is also why it has not been done often. Workfront is designed for sharing, not restricting, so what you are looking to do is difficult.

In our scenario, we have really examined what we thought we needed to restrict and found that it wasn't necessary after all. Additionally you can explore removing access to custom forms or documents and keeping your confidential data there instead of in task updates or tasks themselves.

Just thoughts. Good luck in finding something that works! Doug's idea is definitely intriguing.

NickVa7Autor
Level 9
April 15, 2021

Good points, Alison. Thanks for sharing.