Holistic “read-only” setting for community

Hi Gainsight Team,

After a few deep dives in some threads, including this one: 

I'd like to formally request a built-in Read-Only role or permission level for Gainsight Community.

Use case: our community is built for our customer base, but we also want employees to be able to browse it without posting, commenting, liking, or submitting ideas. We're managing this today with a custom role, but a native Read-Only setting would remove the manual upkeep.

This matters for a couple of reasons tied to how we measure community health:

• Employee activity (likes, posts) can skew our content-engagement KPIs, since those numbers are meant to reflect genuine customer engagement.
• Employees submitting ideas or feedback that reads as customer input muddies the voice-of-customer signal our product and CS teams rely on.

Since another admin raised this exact need in the thread above, it seems like a common enough pattern, any company running a community alongside internal employee access, that a native setting would benefit more than just us.

Thank you for your consideration