QuackbackQuackback Docs
Portal

Portal Features

Control what users can do on your feedback portal.

Portal Features

Control which features are available to users on your public portal.

Accessing Feature Settings

  1. Go to SettingsPortal
  2. Toggle features on or off
  3. Changes apply immediately

Available Features

Public View

Default: On

When enabled: Anyone can view feedback without signing in.

When disabled: Users must sign in to see any content.

Most teams keep this on for transparency.

Submissions

Default: On

When enabled: Users can submit new feedback.

When disabled: Users can only view and vote on existing posts.

Disable if you want to curate what appears (submit internally only).

Voting

Default: On

When enabled: Users can upvote posts.

When disabled: Vote counts still show, but users can't vote.

Useful if you want to share a roadmap without collecting votes.

Comments

Default: On

When enabled: Users can comment on posts.

When disabled: Existing comments show, but new comments blocked.

Disable if discussions get off-topic or you want simpler feedback.

Edit After Engagement

Default: On

When enabled: Users can edit their posts even after receiving votes/comments.

When disabled: Posts lock after engagement to preserve context.

Delete After Engagement

Default: On

When enabled: Users can delete their own posts anytime.

When disabled: Posts can only be deleted before receiving votes/comments.

Public Edit History

Default: Off

When enabled: Users can see when posts were edited.

When disabled: Edit history only visible to team members.

Feature Combinations

Full Community (Default)

All features on. Users can submit, vote, comment, and discuss.

Best for: Products with engaged users who provide quality feedback.

Voting Only

  • ✓ Public View
  • ✓ Voting
  • ✗ Submissions
  • ✗ Comments

Best for: Curated feedback where you control what appears.

Read-Only Roadmap

  • ✓ Public View
  • ✗ Voting
  • ✗ Submissions
  • ✗ Comments

Best for: Sharing your roadmap without collecting feedback.

Private Portal

  • ✗ Public View
  • ✓ Everything else

Best for: Internal feedback or beta programs.

Authentication Requirements

Most features require users to sign in:

FeatureSign-in Required?
View feedbackNo (if Public View on)
SubmitYes
VoteYes
CommentYes

Configure sign-in options in Authentication.


Next: Portal authentication

On this page