Learn the difference between a public and a private organization in Featurebase and which one is right for you.
Written By Markus Palm
Last updated About 2 months ago

By default, your Featurebase forum is public and visible to all of your users who visit it. However, you can also use Featurebase in a private mode between internal team members or select user groups. Learn which one is right for you. 👇
Public forum
A public organization is accessible to everyone who visits your public forum. This means your users can view and submit ideas, view changelogs, and see your Help Center.
Who it's for:
Most of our customers, especially if you want to collect user feedback, share updates, and build a public help center.
Companies that want to share updates and resources with their end-users.
Good to know: You can still limit access to certain feedback boards, changelogs and help articles separately.
Private forum
A private organization requires all visitors to log in to prevent unwanted access and competitors from spying. You have full control over who get access to your whole Featurebase forum.
Who it's for:
Companies who want their organization to be accessible only to internal team members or specific user groups (e.g. beta testers)
Companies that want to discuss feedback, share updates, and have a knowledge base internally
3 authentications are available to give access:
Access to specific email domains or by manually inviting people via email
Access by Microsoft Entra ID
Good to know: If you want to keep your forum public but still want to manage some feedback internally, you can use internal team boards. Posts on these boards are only visible to your organization's admins.
Setting up a private forum

By default, your forum is public. Here's how to switch it to a private forum mode:
Select Private organization
Choose your preffered authentication method(s) and complete the set up
More recommended steps:
Could not load article.
Could not load article.
Could not load article.
Could not load article.
Could not load article.
Could not load article.