Umbraco Workflow
CMSCloudHeartcoreDXP
15.latest
15.latest
  • Umbraco Workflow Documentation
  • Legacy Documentation
  • Release notes
  • Installation
    • Installing Umbraco Workflow
    • Licensing
  • Upgrading
    • Upgrading Umbraco Workflow
    • Version Specific Upgrade Notes
    • Migrate from Plumber to Workflow
  • Getting Started
    • Dashboards and Buttons
    • Submitting Content for Approval
    • Workspace View
    • Notifications
    • Configuration
    • Approval thresholds
    • History Cleanup
  • Workflow Section
    • Workflow Section
    • Active Workflows
    • Approval Groups
    • Content Reviews
    • Workflow History
    • Workflow Settings
  • Advanced Search
    • Advanced Search dashboard
  • Data Generator
    • Data Generator
Powered by GitBook
On this page
  • Related settings and configuration
  • Settings
  • Configuration

Was this helpful?

Edit on GitHub
Export as PDF
  1. Getting Started

Approval thresholds

Use thresholds to configure how many approvals a workflow in Umbraco Workflow requires to be considered complete.

PreviousConfigurationNextHistory Cleanup

Last updated 5 months ago

Was this helpful?

This feature requires a license - learn more about

Umbraco Workflow's default behavior requires one member of an approval group to approve a pending task to advance it through the workflow.

The approval thresholds feature introduces configuration options to set the required number of approvals for a given workflow stage.

The threshold options are:

Option
Description

One (default)

Pending tasks require approval from any member of the assigned approval group.

Most

Pending tasks require approval from an absolute majority of group members. Example: A group with 3 members requires 2 approvals and a group with 4 members requires 3 approvals.

All

Pending tasks require approval from all group members.

The workflow detail UI displays the following:

  • The status of the current task.

  • Approval status for members of the current group.

  • Progress towards meeting the threshold for the current approval stage.

  • Future tasks and the assigned group and its users.

Approving a task as an administrator immediately satisfies the approval threshold for the task, and will advance to the next workflow stage.

When a task is rejected in a workflow stage where the approval threshold is Most or All, existing approvals can be managed via configuration:

  • Existing approvals can be reset, resetting progress toward the approval threshold. In this case, all users in the approval group will be able to approve the resubmitted content.

  • Existing approvals can be kept. In this case, users in the approval group who have already approved the task will not be able to approve the resubmitted content.

Related settings and configuration

Approval thresholds are managed via settings in the Workflow section or in the appsettings.json file. Node-specific thresholds are set directly on the workflow configuration in the Workflow content app.

Settings

Setting
Default
Description

Approval threshold

0 (One)

Sets the global approval threshold.

Rejection resets approvals

false

When true, and the approval threshold is Most or All, rejecting a task resets the previous approvals for the workflow stage.

Configure approval threshold

false

When true, enables setting the approval threshold for any stage of a workflow (on a content node or Document Type).

Configuration

The approval threshold for an individual workflow stage can be set using the control below the stage name. Setting the stage threshold requires the Configuring approval threshold setting to be true.

The settings below can be set from the Backoffice or via settings customization in the appsettings.json file (refer to for implementation instructions).

Workflow's licensing model
Settings customization
Tasklist with approval thresholds
Setting approval threshold for individual workflow stages