Access & Permissions Required
What feature access necessary for workflows is determined by what your user needs to be able to do.
If your user simply needs enough access to be a part of a workflow, participating stages or steps, then the only required feature is 'Workflow'. This will allow your user to participate in workflows and start workflow instances, as well as delete workflow instances that are assigned to them.
If your user needs to be part of an approval process within a workflow, your user will also require 'Workflow Approval' alongside 'Workflow'.
If your user needs to be able to create, edit, or delete workflows, your user will require the the 'Workflow Management' feature. This feature also allows users to manage workflow instances for all users across the account.
Building a Workflow
To begin building a workflow, click on the 'Workflows' option in the navigation bar on the left side of the Revver screen, or by selecting 'Workflow' from the 'All Features' menu.
Next, locate and click on the 'Create Workflow' button near the top right of the Workflows page. This will open up a new workflow for you to begin creating and designing.
Adding Steps
Steps represent the action being performed when the workflow is run. All steps within a single stage happen simultaneously and in no particular order.
All new workflows begin with one stage by default, so you can begin adding steps right away. Add a new step by clicking on the 'Add Step' button.
This will present you with a list of available steps you can add to your workflow.
Choose one from the list and it will appear within your stage and allow you to configure it.
Workflow Assets
In this example, we will be designing the workflow to automatically apply a metadata group to a file. In order for the workflow to know what it will be applying the metadata group to, it needs to be defined in the workflow itself -- this is called a Workflow Asset.
In the example 'Apply Metadata' step in the previous section, the workflow asset can be defined by clicking on 'Select Item'.
This will present you with the asset selection screen. If an asset has already been created/defined in your workflow, it can be selected from the 'Asset' tab. However, since this is the first step in our example workflow, one must be created first.
Assets can be static files or containers that exist in your Revver documents structure, or manual assets that are defined as the workflow is run. For the purpose of this example we will be using a manual asset. Clicking on the 'Manual' tab will allow you to configure the manual asset and what it represents.
Asset type refers to whether the asset represents a single file, multiple files, or a file path within your Revver documents structure. For the purpose of this example, this asset will be configured to represent a single file, limited to PDFs, and is simply named 'New File'. Once configured, click on 'Done' to save it to your Workflow Assets list.
To finalize the configuration of our step, we need to select the metadata group it will apply, whether it will run automatically or need manual user intervention.
If set to 'Manual', a description can be added that an assigned user will see when interacting with this step in the workflow.
Adding Stages
If your workflow requires multiple stages, a new one can be added by clicking on the 'Create Stage' button.
This will add a new stage with no steps in it. New stages will appear in sequential order, but can organized using the arrow buttons at the top right of the stage itself.
To delete a stage, click on the trash can icon.
When to Use Multiple Stages
β
Steps within a single stage are all performed simultaneously. If your workflow requires approval from another user, you need actions to be performed in a specific order, or are utilizing multiple branching stage routes, multiple stages are required.
Stage Configuration
Each stage is highly configurable, allowing you to determine which user or group it is assigned to, timeframe requirements, approval requirements, and more.
Assignees
Workflows require at least one assignee, which can be any user with a full or essentials user with the 'Workflow' feature enabled.
If a single user is chosen, that user is selected as the default assignee automatically. If multiple users are added as available assignees, they can each be selected when the workflow is run. Any user selected as the default assignee will be pre-selected whenever the workflow is run manually or triggered by an automation setting.
Timeframes
Timeframes allow you to set limitations on how long a workflow instance may remain on a single stage, as well as determining what happens when that limitation is met.
For example, if after three days the workflow stage has not progressed, the stage can be configured to:
Move on to the next stage
Repeat the same stage again
Go to a specific stage
Or finish the workflow instance as failed, succeeded, or terminated.
Approvers
Each stage can be configured to require the approval of another user within your Revver account. If the 'Approvers' box is selected, at least one approver is required, but multiple approvers can be selected.
If multiple approvers are selected, you can configure how many are required to approve/deny the stage before moves on. Other options include:
Custom message that is displayed to the approver when assigned to them.
Including a specific asset so they approver can review it directly within the workflow instance.
Upon approval or rejection, the stage can be configured to route to different stages or end the workflow.
Stage Routing
Outside of approvals and time frames, stages can be routed in various ways. A simple workflow that applies metadata may only need one stage and complete once the step has been fulfilled, but in conjunction with an approval step, it could route to a different stage depending on whether it was accepted or rejected.
Each stage within your workflow can be configured to determine which stage occurs next, options include:
Next Stage - The workflow will progress to the next stage in sequential order.
Repeat Stage - The workflow will start the current stage over from its first step.
Go To... - The workflow will progress to the selected stage.
Finish Workflow - The workflow instance will complete with the selected status: Succeeded, Failed, or Terminated.
Metadata Routing - The workflow will progress to a stage based on defined routes and determined by the content of metadata fields on one or more workflow assets.
For more information on Metadata Routing, see the following article.
Finishing Touches & Configuration
Once all of the steps and stages in your workflow have been designed, clicking 'Save' at the bottom of the page will finalize your workflow and make it available for use.
However, here are some additional options available to you within the workflow configuration screen.
Workflow Settings
Outside of configuring individual stages, steps, and assets, the workflow itself has options available to change workflow instance behavior. Located at the top of the workflow configuration page, click on the 'gear' icon to open the Workflow Settings panel.
An overview of each setting can be found below:
Setting | Description |
Active Workflow | Determines if the workflow is active and available for use, or disabled. Disabled workflows cannot be chosen when kicking off workflows manually or through automations. |
Workflow Owners | Determines who can edit the workflow. |
Watchers | Determines what other users, if any, will be included in workflow notifications or emails. |
Notifications | Determines when a workflow will send notifications to assigned users within Revver. These notifications will appear in the notifications 'bell' icon at the top right, or on the users Revver home page. |
Emails | Determines when a workflow will send emails to assigned users in Revver. |
Instance Name | Determines how the instance will be named. By default, all instances are named after the workflow. |
Default Step Mode | Determines if new steps added to a workflow stage default to 'Manual' or 'Automatic' as the selected progression option. |
Complete Stages Automatically | Determines if workflow stages will progress automatically. This is enabled by default. |
Lock 1st Assignee | Determines if a workflow can have its assignee changed after the instance has started. |
Stages Require 100% Approval | If multiple approvers are chosen for stages in this workflow, selecting this option will require 100% approval from any assigned approvers. If one of the approvers rejects it, the workflow will progress through its rejected route. |
Workflows Require File to Start | Locks the workflow so that it can only be started from a file. |
Workflow Requires Directory to Start | Locks the workflow so that it can only be started from a directory. |
Require Approval Note | Approvers will be required to leave a note along with their approval/rejection decision. |
Schedule Configuration | Allows the workflow to be configured to run automatically on a schedule. |
Workflow Preview
For complex workflows, the workflow preview option gives you a flowchart style look at your workflow and the routes it takes through your stages.
Located near the top of the workflow configuration, click on the 'eye' icon to open a preview of your workflow.
Need Help?
Contact Technical Services
To get assistance from our Technical Services team, look for the chat bubble in the lower right corner to connect with our trained AI agent, Fin.
Fin references our entire Revver Help Center to accurately answer your questions, but if you would like to speak to a live technician, simply ask Fin to "Transfer me to a live technician" or select the "Talk to a person" button below Fin's chat answers and you will be immediately transferred to the first available Technical Services team member.
You can also connect with us via email at [email protected].




















