Approval workflows for internal communications put Create vs Approve gates before content can send. How Broadcast Content Hub Queue works, and how to start.
Foundations is free (forever) - purpose built for internal comms and includes everything you need to level up your game (email builder, analytics, pulse surveys and much more).
Learn more about Broadcast FoundationsApproval workflows for internal communications put a review gate between draft and eligibility so creator-only content cannot go live until an approver releases it. In Cerkl Broadcast, that gate lives in the Content Hub. Drafts move to a Queue, an approver marks them Approved, and only then can the piece feed digests and other surfaces that read from the hub.
A Slack reply of "looks good" and a shared doc with six commenters leave no final owner and no status anyone can trust. The Create Content versus Approve Content split turns that ambiguity into a status anyone can read. Broadcast applies it to Content Hub items rather than blast sends.
Picture a benefits FAQ that has to go company-wide before enrollment opens. The communicator drafts in the email tool, pastes a preview into Slack, tags Legal and HR, and waits. Legal replies with a wording change. HR asks for a different effective date. Someone on the channel says "LGTM" on an older version. The communicator sends the version sitting in their draft window, which still has Monday's date.
By Thursday, employees screenshot the wrong deadline. A correction blast goes out, and trust drops another notch. Open rate on the correction looks fine; the original error already trained people to doubt the next company email. That pattern is employee email overload mixed with process failure. Volume is one problem. Ungoverned "approval" is another, with no single status and no record of who signed off on the text that shipped.
The same failure shows up on policy updates and leadership notes. Review lives in chat because the tool has drafts and send, but no Queue. Teams then choose between slowing every send with hallway politics or shipping fast and fixing in public.
An approval workflow for internal communications is a product rule. People with Create Content rights can author and submit; people with Approve Content rights can release. Submitted work sits in a Queue until an approver acts. Approved work becomes eligible for the channels and digests that pull from the content library. The unit of value is eligibility you can trust in the hub.
Sample emails and audience previews serve a different job on a blast. Samples check rendering and copy with a handful of reviewers. Audience preview checks who is on the list. Neither stops a creator from pressing send on the live blast if their seat allows it. Approval workflows solve the "creator cannot publish alone" problem for content that must clear brand or legal before it enters the shared pool.
In Broadcast, that pool is the Content Hub, the same CMS intranet style library that feeds personalized digests and omni-channel surfaces. Permissions split Create Content and Approve Content. An approver who Publishes skips the Queue and lands straight in Approved. A creator-only Publish routes to Queue, where an approver clicks Approve (or Publish Changes from the editor) to release it.
The operational fix is status you can trust. Draft means the item was never submitted, and Queue means it is waiting on an approver. Approved means eligible. Archive and circulation rules still control how long something stays visible, but they do not replace the gate that decides whether it was allowed out of draft in the first place.
The pipeline is easier to trust when each stage is visible.
Drafts. Authors write Stories and Events in the Content Hub (or share a link). Work can stay in Drafts while copy and distribution settings settle. Nothing in Drafts is eligible for digests or channel posts.
Submit into Queue. A creator without Approve rights who Publishes sends the item to Queue. Queue holds submitted work that is not yet eligible. Approvers get Preview and Approve actions from Queue (plus Edit). Bulk Approve exists when several items are ready at once.
Approve. An approver releases the item with the green check or by publishing changes from the editor. The piece moves to Approved. From that moment it can enter News Digests and other Omni surfaces that read the hub, including Content Blocks inside blasts when that path is in use.
Approver shortcut. Someone who already holds Approve Content can Publish and land in Approved without a Queue stop. Use that for trusted leads who own both authoring and release. Keep Create-only seats for contributors who should not control the gate.
Source moderation. External RSS or XML sources can route into Queue when Moderation is on, which is the safer default for third-party feeds. Turning moderation off auto-approves ingested items. That toggle runs on the same approval model as authored content.
Controls and notifications. Content Controls set Queue notification frequency (Never, Daily, or Weekly) so approvers are not dependent on remembering to open the Queue tab. Categories and expiration defaults live in the same Controls area, but they do not replace Create versus Approve.
On Omni AI, omni-channel publishing is the delivery layer after approval. Author and approve once in the hub, then route the formatted version to each employee surface. Personalized AI Newsletters and the MyNews internal communications digest path also pull from Approved hub content, so the Queue sits upstream of personalization.
Broadcast Omni AI helps large organizations deliver personalized communication across email, mobile, Teams, intranet, and more. Content orchestration at scale.
Learn more about Omni AIDecentralized authoring is where this lands first. Regional or function communicators draft locally while brand or legal holds Approve Content, so the company gets speed on intake without every seat being able to make content eligible. Segment permissions can sit beside that model so audience ownership and content approval are both explicit.
Regulated copy needs the same gate for a different reason. Policy and benefits language require a named release step, and the status field carries it, with Queue showing what is waiting and Approved showing what leadership can trust is live. Correction volume falls when the wrong version never leaves Drafts.
Multi-site programs run on the same shape. Plant and corporate teams author into one hub, and approvers clear site-specific items without anyone rebuilding a separate tool per location. Distribution settings and segments still decide who sees what after release.
Third-party intake is the case people forget. Newsroom feeds and partner blogs enter as Stories, and moderation holds them in Queue until someone accepts the headline and summary tags. Auto-approve stays available when the source is trusted and speed matters more than human review.
In each case the job shifts from chasing comments in chat to clearing a Queue with a clear yes or edit path.
You do not need every channel live on day one. You need honest audiences and a clean split between blast hygiene and Content Hub approval.
Get the people layer current first. Live HRIS or directory audiences stop governed content from reaching the wrong roster. The audience sync for internal communications path covers that plumbing. Map who may create versus who may approve before you open contribution wide.
On Foundations, start with purpose-built internal email. Use Audience Manager, targeted blasts, Insights, sample sends to a small review circle, Audience Preview, and Sender Proxies so send-from identities stay controlled. That week retires the worst "approve in Slack, send from Outlook" habit for time-bound blasts. Foundations does not include the Content Hub Queue. Formal Create Content versus Approve Content approval workflows ship on Omni AI with the Content Hub and omni-channel publishing.
When governed Stories and Events are the pain, upgrade for the Queue. Assign Create-only seats to contributors, Approve seats to brand or legal leads, turn on Queue notifications, and keep Moderation on for untrusted sources. Keep true one-shot campaigns on blasts. Use the hub for the recurring content pool that digests and channels share.
If release still means a chat reply on an ambiguous draft, you do not have approval workflows for internal communications. Broadcast earns the label when creator work stops at Queue until an approver makes it Approved and eligible.
That's why we built Foundations. Purpose-built for internal email with all the features you wish you had - drag-and-drop email builder, analytics, employee segmentation and much more. All for free (forever). No credit card, no contracts, no setup fees.
Learn more about FoundationsWhat are approval workflows in internal communications?
Approval workflows in internal communications are review and approve gates that separate drafting from release. In Broadcast, Create Content authors submit to a Queue; Approve Content users release items to Approved so they become eligible for digests and channels.
How does a content approval queue differ from sending a sample email?
A sample email checks how a blast looks for a few reviewers and does not change publish rights. A content approval Queue blocks eligibility until an approver acts, so creator-only users cannot make hub content live on their own.
Are Broadcast approval workflows available on Foundations?
No. Content Hub approval (Drafts → Queue → Approved with Create versus Approve permissions) is part of Omni AI. Foundations includes Blasts, Audience Manager, and Insights, plus sample sends and audience preview for blast hygiene. Teams often start on Foundations, then add Omni AI when Queue approval is the job.
Who can approve content in Cerkl Broadcast?
Users granted Approve Content can release Queue items or Publish straight to Approved. Users with Create Content only can author and submit to Queue. Admins assign those permissions so brand or legal leads own the gate without giving every author release rights.
