Is there any way to set portfolio permissions so members can’t delete or rename projects within the portfolio? Solution needs to be scalable across thousands of employees.
2 Likes
I believe there is no such permissions at the portfolio level, but a member that is comment-only on the project I think won’t be able to rename the project or maybe remove from portfolio… But I am guessing you don’t want them to be comment-only?
1 Like
Hi @KColvin, thanks for sharing your feedback with us! Hopefully this is something we can implement in the future.
I’m moving your thread to the #productfeedback category for the time being to give you and other community members an option to vote for this feature! 
2 Likes
I also have this issue. As Bastien commented, it would solve the problem if we had an option to classify some members as comment-only. In portfolios we have only owner and member options. Is there a way to classify them as a comment or viewer-only? It would be very important.
I’ve updated the title to include your request. Please click the title and vote with the purple Vote button if you haven’t already.
Thanks,
Larry
1 Like
Although the purpose is slightly different, I think it is similar, so I would like to include a link.
1 Like
Yes! Would love more permission levels on Portfolios similar to projects, for example:
- Owner/Admin (can add/remove projects, can add/remove custom fields)
- Editor (can add projects to portfolio, cannot remove projects, can edit custom fields)
- Commenter (can add status updates)
- Viewer (view only, can view workload, etc)
Also:
- Ability to add a user to a portfolio (with a set access level like comment only) AND grant them access to all projects in the portfolio
This is so needed! Team access only gets a user so far. When we have new employees, this would save us so much time. It is so difficult to work out which projects need to be manually granted access.
I feel @Ka_Nishiyama 's suggestions are the most pressing, as either one instantly solves the “Where the F is my portfolio??” and the subsequent hassle both for users and Asana of figuring out what happened and restore it with help of Asana support.
Adding settings also helps, but requires people to set these settings before it is an effective solution for the deletion problem.
Editor not being able to delete feels a bit constrained.
One thing to also take into account is that currently, when someone uses a template that should be added to a portfolio it only gets added when that person has access to the portfolio.
If we’re moving toward access rights I feel these shouldn’t restrict adding projects to portfolio using template settings.
1 Like
Hi everyone, I’m excited to announce we just launched access levels on portfolios! This feature allows you to set your portfolio as view only 
Learn more in our announcement below:
Feel free us know if you have any questions or feedback in our announcement, thanks!
3 Likes