Persist Blueprint Folder Permissions
When you create a project from a blueprint the folder permissions set on a blueprint DO NOT propagate to the newly created project from said blueprint.
Not having this ability weakens the value proposition of blueprints. There is no way to stage a complex folder structure with appropriate permissions without this. You must create from the blueprint and then MANUALLY add the permissions to the required folders post-creation. Not ideal if you have a plethora of directory level permissions needing to be applied.
We should either have a way to retain folder level permissions upon creating from the blueprint or retain those permissions outright.
I'm glad I'm not the only person who is irritated by this. When something is set up or configured in the blueprint section those same settings should be carried over when it becomes a live project. This greatly reduces the value that blueprints offer.
When they release out of Wrike Labs, configurable view settings should also be transferred to the new project that was created from a blueprint.
Thanks a lot for sharing your feedback on Blueprints, Adam Keller & John Bibbs! It will be passed to our Product team 👍
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Any updates from the product team on this? It's rendering the blueprints inferior to the legacy "templates with deferred statues" method as I can't stage which folders these will be dropped into for each team requiring manually setting permissions.
Hi Adam Keller,
The Product team currently has no plans to implement this suggestion. If there are any future updates in relation to this, I'll be sure to let you know.
This disappointing decision significantly reduces the usefulness of the blueprints section in Wrike. Any serious project planning will have to be done in the production environment so we can set permissions on the folders correctly. Blueprints were described as an area where we could plan a project and get everything set up properly while minimizing alerts to the resources working on these projects, and then when we were ready we could move that project into the production area.
For serious project management, the decision to not have permissions from a blueprint persist into the production environment upon creation of the project turns the blueprints section into nothing more than a template repository.
Hi John Bibbs,
Thank you for sharing this feedback, input like this is instrumental for our Product team for their conversations about potential future updates in Wrike. I'll be sure to keep you posted if there is any new information about this suggestion. If you need anything else in the meantime, feel free to reach out at any time.