Learn to restrict your users access to different parts of Featurebase.
Written By Markus Palm
Last updated About 1 month ago
Overview
Learn to restrict end-users' access to control who can see and interact with different parts of Featurebase. You have several options for this:
Public vs private organization: Decide whether your entire organization is open to everyone or restricted to only authenticated users.
Feedback board privacy options: Customize each board's visibility, privacy, and the actions that users can take.
Anonymous actions: Allow users to post, upvote, and comment without signing up, leaving them anonymous.
Post & comment moderation: Review posts and comments before they go live, ensuring quality and privacy.
User-specific access: Restrict access in Featurebase separately for different user groups.
These settings can help ensure that the right people have the right access to different actions and parts of Featurbease.
Public vs private organization
By default, your Featurebase organization is public and visible to all of your users who visit it. However, you can also use Featurebase in a private mode to get full control over what users can access. Learn which one is right for you. 👇
Public Organization:
Visibility: Your public portal is accessible to everyone. All end-users can view and submit ideas, see changelogs, and access the help center.
Ideal For: Companies wanting to collect user feedback, share updates, and build a help center for all their end-users.
Private Organization:
Visibility: Restricted access to selected users. You have full control over who can leave feedback, view changelogs, and access other modules.
Ideal For: Companies wanting to use Featurebase for internal feedback collection and alignment or for those wanting to collect feedback/show updates only to selected user groups.
Authentication Methods: Access by company email, Microsoft Entra ID, or via custom SSO solution.
Learn to switch between public and private organization:
Good to know: If you want to keep your organization public but still want to manage some feedback internally, you can use private boards. Posts on these boards are only visible to your organization's admins.
Feedback board privacy options
You can choose between many privacy settings for feedback boards to help you control the access and visibility of each board individually:
Public Boards (default): All posts are visible to everyone who visits these boards. They’ll also appear in search engines, etc.
Read-Only Boards: Visible to everyone, but only team members can post. Users can only vote/comment.
Private Boards: Only visible to team members and meant for internal feedback.
Anonymous Boards: The board is visible to everyone, but user information is hidden from posts and comments.
Author-Only Boards: Posts will automatically be ‘author-only’ and visible only to team members and the author itself. Ideal for sensitive feedback.
Learn how to modify your board privacy settings:
Anonymous (no log-in) actions
The anonymous actions allow users to engage with your Public Portal without needing to sign up. There are 3 options:
Anonymous Posting: Anyone can submit feedback without signing up.
Anonymous Upvoting (default): Anyone will be able to vote on posts without signing up.
Anonymous Commenting: Users will be able to comment on posts without signing up.
NB! Anonymous upvoting is enabled as a default for all organizations.
Learn to modify anonymous settings:
Post & comment moderation
The post and comment moderation features provide additional control before content goes live on your Public Portal. They’re useful for managing what gets shown publicly, such as filtering out sensitive information in bug reports or handling duplicate or low-quality posts.
Post & Comment Moderation Actions:
Approve: Makes the post/comment visible on your public board.
Mark as Duplicate: Merges the post with an existing one.
Delete: Removes the post/comment entirely.
Discuss Privately with Author: Keeps the post private, visible only to the author on the board.
You can learn to enable moderation from here:
User-specific access
You can restrict access to specific user groups, which is ideal for creating separate product releases or collecting feedback from different audiences. This functionality is available starting from the Growth Plan and can be implemented in two ways:
1. Letting only selected users access Featurebase
If you don't want the Public Portal and widgets to be accessible to everyone on the Internet, you can restrict access to only specific user groups. This can be done by turning your organization private and using SSO to authenticate only selected users.
Learn to set it up:
2. User-specific feedback boards and changelog releases
If you have multiple different products or user groups that are not relevant to each other, you can create separate feedback boards and changelogs for them. This way, end-users see only what’s relevant to them.
For example, Product A users will only see posts under boards they have been given access to, and the same for Product B, C, etc… users.
Learn to set it up: