I would like for a task collaborator to always have comment-level access to the task [or at least be able to customize access at the task level]. This has specifically come up for us now that projects can be set to “viewer” level access. We have a board that receives requests through an Asana form. Anyone in the organization can submit the form. We have had to set the project’s level of access to “commenter” for the entire organization in order to allow anyone who is relevant to one specific task - including the submitter - to comment on the task. This is not ideal. Everyone in the organization really doesn’t need to be able to comment on every task in the board [only the small group of editors/admins - need that]. They need to be able to comment on the right and relevant tasks and adding them as collaborators is the obvious way to indicate that. But as it stands, if the whole org is set as viewers only, they can not comment on tasks unless they are assigned the task.
Thanks
Hi @Jackie_Matuza , why don’t you invite certain members to the project as Commenters while keeping the rest of the org as Viewers?
Hi @Richard_Sather , Since anyone in the org could at any time submit a request to this project, we will eventually have individually added most users to the project as commenters. Which gets back to the original issue that most people should not be able to comment on ALL tasks but anyone who is a collaborator should be able to comment on that specific task because it’s relevant to them.
Hmm, I understand the conundrum, @Jackie_Matuza .
I would then set the project collaborators as Commenters instead of Viewers but also put an internal ‘convention’ or 'best practice ’ in place and simply educate and communicate these rules and expectations of this particular project’s workflow to all stakeholders involved. i.e. Don’t comment on tasks you aren’t a collaborator.
It’s easier said than done, but it can be done.
Additionally, you could make the project entirely private, without any members but a few who could see all form submissions. That way, only collaborators would only see/access their tasks as commenters, but not other tasks in the project. This make work, dependant on the nature of the workflow and use case which, to be fair, I may not fully understand at this point.
Thanks Richard, I’m not overly concerned about people commenting on tasks that are not relevant to them so I think you’re correct that it’s the right path for now to continue with everyone as commenters. I do still think that since collaborator status is set at the task level, that you should be able to set higher commenting permissions at the task level as well.
A possible workaround:
- Create an all-staff team and make it public to company so anyone can join.
- Add the All-staff team as viewer (recently we’re able to add multiple teams)
- Set task collaborator level to Commenter
Thanks for the workaround suggestion, @Jan-Rienk