Workflows are used to require reviews and approvals/rejections for content to before publishing to ensure content stays accurate and up to date. Workflows can be assigned at the folder, group level or asset factory level. As it is not possible to un-delete things in Cascade, it is a good practice to ensure all pages require a workflow for deleting. (As soon as someone has write access to a folder/page they can delete that folder or page.) Although publishers, managers and administrators can bypass workflows, it will help prevent approvers and contributors from accidentally deleting pages or folders.
Workflows include steps, actions and triggers. There are three types of steps—system, transition and edit—and they can be ordered or unordered. Steps are made up of actions. System and edit steps can only have one action (and they occur automatically); transitions can have multiple actions and are dependant on interaction from a user. Actions enable transitions and may have triggers. Triggers may have optional or required parameters that can specify additional information for the trigger (or they may not have any parameters). There are several pre-configured triggers for use in workflows. Common triggers include: e-mail, assign, publish and delete. A full list of triggers is available in the Hannon Hill Knowledge Base.
Workflows steps can be assigned to individual users or to groups. If assigned to groups, any individual in the group can complete/respond to the workflow.