In the HCMS you can build custom workflows for your content and assets. Any user with Owner or Developer permissions on the HCMS can manage Workflows. If a user has Publisher access in the HCMS, they will be able to view the Workflows screen but will not be able to manage Workflows.
Default Workflow
If there are no custom workflows set up, there is still a default workflow for your content and assets. With this default workflow:
Owners, Developers, and Publishers can publish, decline, archive, and create drafts for content and assets
Authors can create drafts and submit content and assets
Readers can view content and assets
Understanding a Workflow
Workflows are comprised of steps
On each step, there are transitions
These steps and transitions define the flow of content or assets through a workflow
There can be as few as one (Published) step, or as many steps on a workflow as you need
Step
The Declined step is an example of a single step for a workflow:
Status
Statuses include:
Archived
Draft
Submitted
Declined
Published
Each status has a separate step in this workflow
Transition
In this example, Archived, Draft, and Submitted are each a transition on this step. Published is a status that is not currently a transition on this step, but it could be added as a transition to this step if desired.
In the example, we have a step of a workflow for the Declined status. When looking at this step of the workflow, you can read this as a content item or asset that has a declined status that can be transitioned to:
The Archived status if the user changing the status is a Publisher, Developer, or Owner (not visible in this current view) for the permission set
The Draft status by any user
The Submitted status if the user changing the status is an Author for the permission set