TL;DR: Approval Flows in Foleon give your teams structured control over publishing by allowing non-publishers to request approval and enabling admins to enforce pre-publishing checklists.
What are approval flows?
Publishing Approval Workflows in Foleon are built to streamline collaboration and make publishing more reliable, without introducing unnecessary governance overhead. Managed in the Approval Hub, they help organizations bring structure and clarity to the final stage of content production.
Approval Flow > Publishing gives Enterprise teams the governance tools to control what gets published, when, and by whom. Until now, teams relied on manual processes, increasing the risk of errors, delays, and non-compliance. This feature introduces scalable, structured publishing control aligned with Enterprise needs.
Where can you find it?
You’ll find the new Approval Flow under Admin Console → Content Governance → Approval Flow, where you can enable two optional controls:
How do Approval Flows work?
Enable publishing approval
Allow users without publishing rights to submit Docs for review. Someone with publishing rights can then approve and publish the Doc. This introduces a clear reviewer flow for larger teams.
This way, you can hit the request approval button when you are on the editor and get to the publishing stage. You can select users with Publishing rights in the modal. This request will trigger an email notification and appear in your new notification panel.
Here’s how it works:
- Notifications are not currently real-time so to see new notifications users needs to refresh the page.
- New notifications appear in the panel with a blue dot indicator. We do not show notifications if they are older than 7 days
- Once the related action is completed (e.g. publishing a Doc - also by someone else), the notification is automatically marked as resolved — the blue dot disappears, and the notification counter updates accordingly.
- Resolved notifications remain visible in the panel (for now), giving users a short history of recent activity.
- The notification counter only reflects unresolved items, ensuring clarity on what still requires attention.
This version of the panel is part of our Beta experience, and we’re already exploring ideas like resolved/unresolved filters and real-time updates for future iterations.
Set up a pre-publishing checklist
Admins can set a check list before publishing this would require users with publishing rights to complete a pre-defined checklist before they’re allowed to publish. This helps maintain content standards and prevents rushed mistakes.
Admin Console:
Editor:
Why should you use Approval Flows?
Approval flows bring structure to the final step of content production. Teams can replace scattered email threads and unclear handoffs with defined approval flows that route content to designated stakeholders. Combined with customizable pre-publishing checklists, organizations can build their specific standards—brand guidelines, compliance requirements, accessibility checks—directly into the publishing process. The result: clearer communication, fewer publishing delays, and better visibility into what gets published when.