Public Blueprints

What is the best way to create and access shared blueprints? We have blueprints saved in multiple locations, some of which others can see but it's not obvious what blueprints each person has. In addition, we just discovered some were saved to our shared space, however, it is not intuitive to navigate there to see those blueprints. What is the best practice to create shared blueprints that are easily viewed and used by teammates?

Find more posts tagged with

Comments

Amy Hunter

Hi @Amanda Olson we save the majority of our Blueprints at the account level. I have set up folders for each team and point teams to this area when they want to set up a Blueprint. The folders help to group the Blueprints together and make it easier for teams to locate theirs. I include all of this information in the training materials we send out to new users and include it within our Knowledge base in Wrike. If I need to share a blueprint with a team member or need feedback I usually @mention the user in the blueprint. Or sometimes I will send an email with a link to the blueprint but I like to keep most of the communication in Wrike.

Sarah Dungey

Hi Amanda,

We are trying to move more towards space-level blueprints so that things are more decentralized, but in the Account-level Blueprints area, we set up a folder for each team and set the permissions on the folders to be the "My Team" internal user group so that everyone has access to the Blueprints within the team folders.