Skip to main content

Create a template-specific Approval Flow

BindTuning Team avatar
Written by BindTuning Team
Updated over 2 months ago

Template-specific approval flows are unique approval sequences that are defined during the template creation process and are designed to be used exclusively with that particular template. This allows for highly tailored governance and approval steps for specific types of workspaces provisioned from that template.

This article guides you through the process of defining these unique flows during template creation in Automate365.


Approval flows during template creation

To create a template-specific approval flow, you must be in the process of creating a new template. If you haven't started yet, please refer to our guide on Understanding Templates before proceeding.

As you progress through the Automate365 template creation wizard, you will encounter the "Approval workflow" step within the left-hand navigation of the wizard.


Define a template-specific Approval Flow

Within the "Approval workflow" step, you can define your unique approval sequence:

  1. Click the "+ Create now" link.

  2. This action will open the same intuitive approval flow configuration interface that you use for creating global, reusable approval flows. Here, you can:

    • Define the sequence of approval steps (up to three steps).

    • Specify who will approve each step.

    • Add a custom request message for each approver.

    • Use the "+ Add step" button to include multiple approval stages.

  3. After configuring your flow, you will be presented with options to define its scope. To ensure the Approval Flow is exclusive to this template, select the option "Use only for this template". Choosing this will save the flow settings as part of this template's draft.
    ​

No further action is needed for the approval flow itself at this stage; the template-specific flow will be saved automatically when you finalize and save the template draft. Once the template is published and used, this approval flow will be automatically applied to all new workspaces provisioned using it.

If you select "Save to Approval flows", a reusable flow will be created and stored in your Approvals list, accessible for use across multiple templates.


Did this answer your question?