Default Access Role for Project Owners
It would be beneficial if we could specify a custom access role to be assigned to project owners instead of defaulting to "Full" access.
As an example of this would be as follows:
I do not want people to be able to delete projects out of our system with a few exceptions. If something needs to be deleted I want my PMO staff to do review the deletion request and to be the one who actually deletes. This is for data integrity and lessons learned. If a project was canceled I don't want it deleted, I'd like to document why it was canceled and then learn from it for the future.
When a project owner is assigned to a project they are automatically given full permissions which means they could delete the project. Because of this, I turned off the permission to delete folders & projects under access roles to avoid that.
However, this is causing an unforeseen issue that I need to solve. There are areas (i.e. my personal space) where I cannot delete anything nor can I change the permissions for that space.
In a world where I am trying to leverage automation and eliminate as much manual work as possible my team will have to go back to manually managing permissions which is a step backward.
The solution for this would be to have a role that can be designed as the default role for a project owner so you can specify what a PM can and cannot do to their projects in the system.
This is still an issue and I have not found a work around. Has anything been done on this?
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Basudha Sakshyarika Wrike Team member Become a Wrike expert with Wrike Discover
Hello,
I share the same requirement and requesting it accordingly!
Upvoted!
Kind Regards,
Kareem
I'm upvoting this as well.
When access to projects or folders is shared through user groups with a role other than "Full," assigning a task to a person from that group automatically upgrades their access to "Full" for the project.
This is problematic because the "Full" access role includes the permission to add a parent folder. As a result, the person can add a parent item, which unintentionally shares the project with users from another project or space. Even after removing the parent, the access remains—this can happen automatically and lead to serious access control issues.
To prevent this, we would need to restrict the "Full" access role. However, doing so introduces limitations in personal spaces, as described above.
Hi 👋 Kareem Noureldeen, thank you for supporting this suggestion and providing your upvote, and Lukas Budavičius thanks for clearly explaining your use case and highlighting.
We will make sure your comments are forwarded to the responsible team. If there are any further updates or developments regarding this matter, I’ll be sure to share them here 👍
Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Rohan V Wrike Team member Become a Wrike expert with Wrike Discover
I’m experiencing the same issue and vote to change the Default Access Role for Project Owners so it does not grant Full Access. This is causing problems with my projects and creating extra work for me, as I have to fix it for every single request I receive.
Thank you for the feedback, Sarah Maldonado, and welcome to the Wrike Community. I have shared your feedback with our product team for consideration. 👍🏽
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Basudha Sakshyarika Wrike Team member Become a Wrike expert with Wrike Discover