Why is "edit" access needed to add projects to a Portfolio?

Does anyone know why you need to have “edit” access to a project in order to add it to portfolio, given the portfolio doesn’t seem to edit the project in any way.

A number of my PMs have set me to “comment only” and now I have to request edit rights to their project in order to add their project to our portfolio view, which strikes me as very strange, given I have no need to edit their project.

Is this a possible bug?

Hi @Curtis_Naphan and thanks for reaching out in the Forum!

You’re completely right, as it stands it is necessary to have projects edit right in order to add them to a Portfolio. Comment Only allows you to consume project content, while edit rights allow you to action, modify or share the project content. We consider adding a project to a Portfolio as moving/sharing the project, hence while we require you to have edit rights!

Hope this helps to clear things up, but if you have any follow-up question or comments, please let me know, I’ll be more than happy to help!