Bulk change Help Center audience targeting | Community
Skip to main content
Submitted

Bulk change Help Center audience targeting

Related products:Knowledge & Help Center
  • April 20, 2026
  • 3 replies
  • 73 views

  • Would be great to be able to bulk change Help Center article visibility
  • Editing the audience on each article individually is time-consuming and frustrating
  • Ideal end state: be able to bulk change article audience permissions by collection or by selecting multiple at a time (similar to the way we can currently use the bulk action “Change Fin audience”)

3 replies

Roy
Top Expert ✨
Forum|alt.badge.img+7
  • Top Expert ✨
  • April 20, 2026

Hey ​​​​​@Johanna Bunn 👋,

Fully agree—bulk editing for Help Center visibility would be a massive game-changer. 🚀 The current workflow is a bit of a slog, to say the least.
 

I actually just dug into the Intercom API to see if there was a sneaky workaround, but even there, article audience targeting isn't exposed for updates. 🛠️ When you can’t even automate it via code, you know it’s a bottleneck that genuinely needs addressing.
 

I’d also suggest allowing Audience Rules at the Collection level. Imagine moving a "Beta" collection to "Public" and having every article inherit those permissions instantly. In this AI era, we shouldn't be stuck clicking through articles one by one like it's 2015. 🖱️💤

Fully supporting this request! ✅
 

Cheers,

Roy 🇬🇧


  • New Participant
  • April 30, 2026

Yes please!!! We just had to edit 1,100 articles by hand to set the right audience for each one. 


I hope this gets addressed soon. Every time we have a beta launch, or any situation where we need to gate articles, the process of segmenting the Help Center audience is extremely manual and time-consuming. 

It would be great to see a bulk action for Help Center audience that mirrors what already exists for Fin audience — select multiple articles, choose the audience, done. Even better would be collection-level audience inheritance, so articles automatically pick up the visibility settings of their parent collection. That alone would cut our beta-to-public workflow down dramatically.