Skip to main content
Sudhanshu
Gainsight Product Manager
September 16, 2026

Introducing Feature Previews for Gainsight CC

  • September 16, 2026
  • 5 replies
  • 126 views

Based on popular feedback, we are changing how we release new features and platform improvements to your community. Instead of rolling out changes immediately, we are giving you the opportunity to preview and test them before they go live.

To support this, we have expanded the Open betas page in Control to include Feature previews.

Here's what you can expect:

  • A toggle you control. Front-end changes now arrive switched off. You decide when to turn them on.
  • Somewhere safe to test. Enable the preview on your sandbox, see what it does to your styling, fix what needs fixing, then enable it on production when you're ready.
  • A clear deadline. Each feature preview stays active for a limited period of time. After that it becomes standard for everyone and the toggle goes away.

What counts as a preview

Not every release needs this, and wrapping all of them in a toggle would just be noise. A preview is for changes that could interfere with work you've done: member-facing updates that touch front-end structure, CSS class names, or layout, any change that could affect a customized integration.

The first two previews are now live: accessibility improvements to the category mega menu and to the Section Categories widget on knowledge base pages. Both make keyboard and screen reader navigation considerably better, and both touch markup, which is exactly the kind of change worth letting you test first.

You can find feature previews in Control → Settings → Betas and Previews.

Feature previews stay active for a limited period of time. This time can be used to preview, test and prepare for communications on the upcoming changes.

If you hit something during a preview that looks like a genuine bug rather than a styling conflict, that's different, raise a ticket and we'll treat it as one.

Open betas remain unchanged

If you already use the betas page, nothing there works differently. Open betas are finished features that are still evolving, you can switch them on and off whenever you like, there's no deadline, and support covers them.

 

    5 replies

    AndrewK
    Helper ⭐️
    September 16, 2026

    This is great! I tried it out in our Sandbox and the mega menu update does break our menu CSS, so this really saves us some headaches. Thanks for adding this feature.

    Andrew
    Suvi Lehtovaara
    Helper ⭐️⭐️
    September 17, 2026

    This is great, thanks!

    However, I feel it would be useful to have a link to a documentation of the feature → it would be easier to understand what can be excepted to happen :)

    https://yhteiso.elisa.fi/
    Gaby
    Helper ⭐️
    September 17, 2026

    I like this idea!

    Gaby (Client Engagement & Community Manager @ Benevity)
    KellyBebenek
    Helper ⭐️
    September 17, 2026

    It would be helpful if each of the feature previews would link to an article that provided an overview of what it is and how it worked with screenshots.

    For example, this preview:
     

    Accessible Section Categories (Knowledge Base)

     

    This feature will be enabled in 27 days

    Improves headings, lists, and keyboard and screen reader support in the Section Categories (Knowledge Base) widget on knowledge base category pages.

    I don’t have enough information to know if I should turn it on and off. Can you link a help article or product update so we could get more information.

    sleslie99
    Contributor ⭐️⭐️⭐️
    September 17, 2026

    100% agree Kelly!!!

    I love working with communities of people- online and in person!!!