Add Portfolio Permissions like read-only/commenter; prevent users from removing projects from portfolio

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.

1 Like

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! :slight_smile:


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.



1 Like

Although the purpose is slightly different, I think it is similar, so I would like to include a link.