Approval Workflow
Separate saving from publishing and give teams a safer editorial workflow.
React Bricks supports both working copy and approval-based workflows, so content can be reviewed before it reaches production.
Approval workflow in React Bricks
What it is: An approval workflow separates drafting, saving, reviewing, and publishing so content changes do not go live before the right people approve them.
How React Bricks handles it: React Bricks supports working copy and approval-required modes, letting editors prepare changes while authorized users review and approve them before publication.
Why it matters: Enterprise websites, regulated teams, multilingual sites, and larger content operations can keep review and governance inside the publishing flow.
How it works
React Bricks gives you two workflow modes, depending on how much review and control your team needs.
Working copy
With the working copy workflow, saved content does not immediately become live. This means editors can keep working on a page without affecting what is currently visible on the production website.
When you save a page, a separate working copy is created. Once the page is ready, editors can commit the changes and make them available for deployment.
This is useful when teams want to decouple day-to-day editing from what is currently published, without introducing a formal approval step.
Approval required
The approval workflow builds on the working copy model by adding an explicit review step. When an editor commits a page, it is not merged into production immediately.
Instead, a user with approval permission must review and approve the changes before they can be published. This gives teams more control when content must be checked before it goes live.
How to enable the workflow
If the Approval Workflow add-on is enabled, you can configure the desired behavior directly from the dashboard.
- Working Copy: saving and publishing are separated, so in-progress content stays out of production until it is committed.
- Approval required: once content is committed, it must be approved by a user with the right permission before it becomes visible.