cs-icon.svg

About Workflows

A workflow is an order of steps to define the roadmap for a process. This enables users to maintain a systematic approach for reviewing and approving content.

Note: You can create branch-specific workflows, i.e. you can add multiple workflows for a content type, with each one linked to a distinct branch.

For example, in a content development team, creating content for any enterprise requires a clear understanding of the requirements as well as the flow of content from one stage to another, until the time it is published. As content can be worked on by various team members, it is important to streamline the process to maintain consistency and improve the overall quality of all digital properties.

This is where Workflows come into play.

Workflows enable you to streamline the process of content creation, review, approval, and publication. You can manage the flow of content throughout your project lifecycle. With workflows, you can define stages through which your content needs to go, assign entry stages to users, add publishing approval rules, and do a lot more.

Before we move any further, it is essential to know that:

  • Workflows are available only if they are part of your plan. 
  • Only the stack owner, administrator, and developer can create workflows.

After you define a workflow for content and assign a user to work on that content for the next workflow stage, that user receives this assignment in the form of “Workflow Tasks.” Then, through the “Tasks” page the user can access the content and move the content to another stage for further process.

To know more about Workflows, please go through our guides mentioned in the “More articles” section.

Was this article helpful?
^