Skip to main content

7.17.2026 Release Notes

New Reach calendar, post creation, and compliance rules plus a minimum-score approval gate

Written by Daisy Akinbo

Content Calendar

Reach now includes a dedicated Calendar page so you can view your scheduled and published social posts over time. The calendar carries over the streak indicator and lets you toggle between My posts and a Company-wide view, making it easy to plan your content cadence and see what's going out across your team.

More Ways to Create A Post

The "Create new" experience in Reach now supports additional ways to generate content:

  • Generate from a URL — turn a link into a ready-to-edit social post.

  • Generate from a file — start from an existing asset, including files pulled directly from your OS Library.

We've also added a full set of generation controls so you can shape the output before it's created, including expression style, post length, "spiciness" level, tone/energy, and toggles for including emojis and hashtags, plus additional advanced options.

Reach-specific Brand Guidelines & AI Policies

Compliance scans on Reach social posts now use brand guidelines and AI policies scoped specifically to Reach. Admins can configure a Reach-specific brand guideline in Company Settings (it falls back to your organization's default when none is set), and AI policies can be scoped to apply to Reach social content. This ensures social posts are reviewed against the right rules for the channel, rather than policies meant for other content types.

Filter Search and Notifications to Reach

You can now narrow both search and your notifications to Reach. Reach-mode search focuses on your social posts and their associated content, and a new Reach filter in the notification center lets you isolate Reach-related activity. Your standard Library search and notifications are unchanged.

Approvals

Admins can now configure a minimum required compliance score as part of an approval flow. If an asset's scan score is below the configured threshold, it can't be submitted for approval yet, with clear messaging on why it's blocked and what score is required. Combined with score-based auto-approval settings, this lets you enforce a quality and compliance bar before content enters the formal review pipeline and reduces wasted review cycles on assets that aren't ready.

Did this answer your question?