---
title: "Attaching a Comala workflow to a Confluence Blueprint"
canonical: "https://support.appfire.com/space/CDML/649828206/Attaching%20a%20Comala%20workflow%20to%20a%20Confluence%20Blueprint"
format: markdown
---
> Macro (aura-html)


## Overview

Content created with a blueprint with an attached workflow template in a space automatically has the workflow applied to documents when the workflow

- is applied as a space scope workflow in the space

> ℹ️ The blueprint workflow has a content label filter that filters the workflow application using template label

The workflow attached to the Blueprint is added to both

- new content created using the Blueprint
- any existing content in the space created with the Blueprint

[Detaching the workflow](https://appfire.atlassian.net/wiki/spaces/AWPD/pages/617493302) from the Blueprint disables the space workflow and removes the workflow from the existing content.

A space administrator can also customize the attached workflow for the space using the **Edit workflow** option in the Document Management dashboard

## Attaching a workflow to a Blueprint> Macro (anchor)



A space administrator can attach a Comala Document Management workflow to an individual Blueprint in the space tools **Templates** dashboard. 

For an individual Blueprint

- choose **Attach Workflow**

![image](media://15b54dea-ef51-45d6-b6f2-7b54aec96055)

- choose a Comala workflow from the dropdown menu

![image](media://fe7aed5a-25df-483f-9c4e-15dc4190f15a)

> ℹ️ For a workflow to be available, it must be added to the [global workflows templates dashboard](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649530159) and active.

- choose **Attach**

The workflow is added to the space tools Document Management dashboard as an active space workflow.

![image](media://d9119ae3-a313-4c5c-8e63-c4b7a564ad3a)

- existing content created using the Blueprint has the attached workflow applied (if the label added as part of the Blueprint has not been removed)
- any new content created using the Blueprint has the workflow automatically applied

> ℹ️ The method of applying the attached workflow is actually by using a space workflow with a [content label filter](https://appfire.atlassian.net/wiki/spaces/CDML/pages/650154022). The blueprints all have a label and the attached workflow is applied to content with this label.

## Detaching a workflow from a Blueprint> Macro (anchor)



If you want to remove a workflow attached to the Blueprint in a space.

In the space tools **Templates dashboard**, for the individual Blueprint

- choose **Detach Workflow**

![image](media://414c5a0f-14b3-4eee-9ad7-67b1b6cdc590)

> ℹ️ Confirm the removal of the workflow from the Blueprint using the **Detach** button in the popup dialog box.

Detaching the workflow from the blueprint does not remove the workflow from the space tools Document Management dashboard. The space workflow is simply disabled.

![image](media://8375a601-355b-4282-8573-467de2335bbe)

> ℹ️ Any existing content created with the Blueprint no longer has this workflow applied.

## Page Template variables

> 📝 Page template variables cannot be updated by Comala Document Management.

However, template (Blueprint) variables can be referenced in a Comalatech workflow, if the variable is placed in the [Page Properties](https://confluence.atlassian.com/doc/page-properties-macro-184550024.html) macro.  
For more details on how to reference page properties

- [Page Property References](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649728272)

## Related Links

- [Blueprints](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649890383)
- [Page Property References](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649728272)

**Atlassian**

- [Page properties](https://confluence.atlassian.com/doc/page-properties-macro-184550024.html) macro