Use blueprints to jumpstart your team’s work

Access blueprints

Cloud Accelerator managers can create, edit, and publish blueprints from the blueprint management page. To access the blueprint management page, follow these steps:

1. Open the workspace dropdown from the left-hand side of the Lucid Home Page.
2. Click Cloud.
3. Select Blueprints from the navigation menu on the left-hand side of the page.
   

Manage blueprints

From the blueprint management page, you can create new blueprints or access and customize existing ones. Check out the sections below for more details on how to manage blueprints in the accelerator.

Create a blueprint

To create a new blueprint, follow these steps:

1. From the top-right corner of the blueprint management page, click Add a blueprint.
2. Click Add blueprint under the blueprint you want to add.
   • You can choose from Lucid-built blueprints such as “Sprint execution” or create a custom blank one by clicking Use under “Start from blank”.

Customize an existing blueprint

Click Customize on an existing blueprint from the blueprint management page to change the name, edit the description, or edit templates.

Change name or description
To change the name or description of a blueprint, follow these steps from the blueprint’s customization page:

1. Click the three-dot menu to the right of the blueprint’s name and description.
2. Select Edit details.
3. Type a new name or description.
4. Click Save.

Edit a template
To edit an existing template in a blueprint, click Draft changes or Edit draft on the tile of the template you want to make changes to. The Lucid document will open in a new tab and you can make changes as needed. A popup at the top of the page will appear that states “Editing blueprint template”.

Add a new template to a blueprint

After creating a blueprint, follow these steps from the blueprint’s customization page to add a template:

1. Click the plus sign to the right of “Templates”.
2. Select from the following options:
   • Browse template library to choose from a list of pre-built templates
   • Start from a blank Lucidspark board
   • Start from a blank Lucidchart document
3. Type a title under “Template name”.
   • The template name must be unique to the blueprint. A message will appear underneath the text box if the name is already in use.
4. Click Done to close the modal or Edit template to open the template in a new tab.

Any templates you add to a blueprint will be marked as a “Draft” until you share or update the blueprint, signifying they have not been shared with any teams.

Archive a blueprint

To archive a blueprint, follow these steps from the customization page of the blueprint you want to archive:

1. Click the three-dot menu to the right of the blueprint’s name and description.
2. Select Archive blueprint.
3. Review the team categories that will be impacted by archiving the blueprint.
4. Click Archive.

Teams who had access to the blueprint will not be able to create new workflows from the blueprint once it has been archived, but existing workflows won’t be impacted.

Share a blueprint

Cloud Accelerator managers can publish blueprints to share them with teams in the accelerator so they can access them from their team hub. To share a blueprint, follow these steps from the blueprint’s customization page:

1. Click Publish blueprint to the right of the blueprint’s name and description.
2. Select whether you want to publish the blueprint to all teams within the accelerator or if you want to share to specific teams or team tags.
   • If you publish to specific teams, search for and select teams or team tags using the dropdown that appears.
3. Click Publish blueprint.

Teams who received the blueprint can now access the blueprint and any templates within it from their team hub.

Publish updates to a blueprint

If you make changes to a blueprint such as adding, removing, or editing a template, you can publish those changes to any teams who have received the published blueprint.

To publish updates made to a blueprint, follow these steps from the blueprint’s customization page:

1. Click Publish blueprint updates to the right of the blueprint’s name and description.
2. Select whether you want to publish the blueprint to all teams within the accelerator or if you want to share to specific teams using team tags.
3. If you select a different option than when you initially published the blueprint, it will override your previous selection. For example, if you initially select to publish to every team, but later choose to publish to specific teams, any teams not selected will lose access to the blueprint.
4. Click Publish blueprint.

Teams can now access the updated blueprint and corresponding templates from their team hub. The updates will not impact any existing documents teams are using, only future workflows created from the blueprint.

Manage access to a blueprint

After a blueprint has been published, you can update which teams have access to the blueprint by following these steps from the blueprint’s customization page:

1. Click the share settings icon to the right of the blueprint’s name and description under the three-dot menu.
2. Using the dropdown menu, add or remove team tags to adjust who is receiving the blueprint.
3. Click Publish blueprint.

Unchecking the box next to a team tag removes the blueprint from the team hub of any teams associated with that tag. This won’t impact any existing documents teams are using, but affected teams won’t be able to create new workflows from the blueprint.

FAQ

How do blueprints differ from corporate templates?
Blueprints bundle multiple templates into a standardized, reusable package that Cloud Accelerator managers can publish for specific teams to use.

Corporate templates, by contrast, are standalone Lucid documents used for consistent structure or branding, broadly accessible and managed through the template gallery.

Who can create and access blueprints?
Only Cloud Accelerator managers can create blueprints. Teams that have been added to an accelerator can access blueprints created by accelerator managers if the blueprint has been published to their team.

Give feedback on this article