What to do after installing a blueprint

After installing a blueprint, review what it created, then make it yours: check the collections and their fields, shape the pipeline stages to your process, check each automation before it runs on real entries, and connect anything the automations depend on, such as a mailbox. If the install was a mistake, the whole installation can be removed in one step.

Requirements

• A role that can edit collections, pipelines, and automations in the business.
• A blueprint already installed; see Install a blueprint.

Steps

1. Read the summary of what was created. A blueprint (elsewhere: template, app) installs a set of components together: a folder, collections, their stages and pipelines, automations, and sometimes email templates. The install reports each one. The CRM blueprint, for example, creates Companies, Contacts, Leads, Deals, and Notes & activities in a CRM folder, a default pipeline for each of the four main collections, and a lead conversion automation.
2. Check the collections and their fields. Open each collection and compare its fields with the facts you keep. Add the fields you need. Some fields a blueprint installs are protected: you can rename them and change their help text, but you cannot archive them, because the blueprint relies on them. See Fields: built-in and your own.
3. Shape the stages. Rename, add, or reorder stages in each pipeline so they match how work moves in your business. Stages vs option field vs status explains what stages are for.
4. Check each automation before relying on it. Read its trigger and steps, and run a test. Check which sources it listens to; an automation on new entries fires only for the sources it is set for. See Create and activate an automation.
5. Connect what the automations need. An automation that sends email needs a connected mailbox; see Connect a mailbox.
6. Give the team access. Decide which roles work in the new collections and invite the people who need them.

Notes and limitations

• Removing an installation archives every component it created, in one step. Do it before you have built on top of the components, since your own work that depends on them is affected too.
• Choices made at install are fixed. The CRM blueprint's variant, a sales CRM or a CRM with orders and a product catalog, cannot be changed after installation.
• The CRM blueprint is already there. It is installed when a business is created, so check what is installed before adding it again.
• Default status. Collections from the CRM blueprint save new entries as published rather than draft.

Related

For deeper changes, such as reshaping a collection or replacing an automation, see Adapt a blueprint to your business. For what blueprints are, see What a blueprint is.