Skip to main content

Has anyone else opened up parts of their private community to the public?

  • March 17, 2026
  • 2 replies
  • 48 views

meredithw

Hi! My team is looking at making select pages in our customer community publicly viewable. These include user profiles, homepage, certain discussions, and events, all of which previously lived behind a login. The goal is more discoverability, showcasing the value of the community to prospects, etc., but there are concerns we want to address before we move forward.

A few things I'm trying to figure out:

Customer trust: we have always been a private, customers-only community, so our members posted in a space they assumed would always remain this way. How did you approach communicating this kind of change? We’re of course planning to offer to change any profiles or remove/edit discussions upon request before going live in a community post, maybe also an email. Any messaging that landed really well (or really poorly)?

UX weirdness: When you have a mix of logged-in customers and anonymous public visitors on the same pages, things can get a little awkward. Did anything unexpected crop up in the experience that you had to scramble to fix or explain? Or that caused major customer annoyance? 

General lessons learned: Anything you wish you'd done differently, or something that worked better than expected?

We're trying to be really thoughtful about this and make sure our customers feel respected through the transition/are not super put out or inconvenienced, so any firsthand experience or advice is super helpful. Thanks in advance!

2 replies

mitchell.gordon
  • Helper ⭐️⭐️⭐️
  • March 17, 2026

I have run both closed and fully open communities. Opening things up will be great for a support community.

 

UI UX wont change based on customer permissions unless you have some very unique code in there. Biggest thing will be reminding them to log into the site (once there) and make sure SSO is setup properly.
More people will find your community if its open. Answers and discussions can be searched which will greatly help metrics (unless you turn indexing off).
Communicate with your super users and see if they like the idea. If you tick off your super user base, that is when you will see a negative impact.
Remember, you are making decisions based on what others will want/interact with. Poll them and ask them questions to be sure you are giving them something they’d want.

 

Biggest thing not on this list, spam.
You will need to setup a spam mitigation program. You will need to really expand your banned words, banned username possibilities and I would highly recommend having the AI moderation bot turned on.


  • Contributor ⭐️⭐️⭐️
  • March 17, 2026

Hey ​@meredithw! I just went through this process with the community that I manage. 

To protect customer trust, we worked with legal and security to archive all prior customer content in a private forum, giving customers the option to make specific posts public. We hid company names on profiles and communicated these changes months in advance. We also made clear what was publicly visible to prevent any accidental exposure of sensitive information. We communicated this months in advance in multiple email campaigns, and set up a FAQ page in the community. 

The hardest thing I encountered was custom roles being automatically assigned. While Gainsight has the tools to be able to set this up, we didn’t have a good solution on our end to properly define customer vs not customer via SSO so it led to a duration of manual efforts that has now been solved (wahoo). 

Another thing to flag with your leadership team is how a public community will impact your community health metrics. For example in a public community space you might notice an increase in unique visitors but active users could drop due to the increase of “lurkers”. We also saw a drop in logged in visitors and have since added a HTML widget for logged out users reminding them to log in. 

Happy to chat more 1:1 about this if that’s at all helpful! I’ve spent MONTHS on this and have lots of notes to share, am still learning :)