Content Flow workflows can be enabled globally or on a per-space basis.

By default, Content Flow workflows are enabled on all the spaces in your site. Use the steps below to learn how to change this setting. Note that by disabling workflows in a space, you still have access to Content Flow reviewing and archiving as well as scheduling a page for publishing. 

Determine if you have System Administrator privileges

In order to configure Content Flow workflows globally, you must be a System Administrator.

Access the Brikit Content Flow Settings Page

A site administrator can configure the app by:

  1. Clicking on the Confluence Administration cog/gear icon
  2. Selecting General Configuration
  3. In the sidebar menu, under the heading Brikit Content Flow, click Content Flow Settings 

Edit the Settings

Click the edit button.

Globally Enable or Disable Workflows by Default

If "Enable Workflows By Default" is on (the initial installation state), this means that all spaces in the site will have Content Flow workflows enabled. You may still go to an individual space and disable workflows. This is described below.

If "Enable Workflows By Default" is off, then Content Flow workflows are disabled in all spaces. With this setting, you will need to enable Content Flow workflows on a space-by-space basis.

Enable (or Disable) Workflows in a Space

Visit the space in which you want to enable or disable Content Flow workflows and take the following steps:

  1. Open the Confluence Menu and find the Space Tools in the lower left corner. 
  2. Click Space Tools and select Overview.
  3. In the backend, Click the Apps tab, and then Available Workflows

Check the 'Enable (or Disable) Workflows For This Space' Checkbox

If "Enable Workflows By Default" is on (step 4, above), then check the "Disable workflows for this space" checkbox to turn off Content Flow workflows for this space.

If "Enable Workflows By Default" is off, then check the "Enable workflows for this space" checkbox to turn on Content Flow workflows for this space.


If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the Steps block above to narrow the gap between the two blocks.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.