Feedback hub setup

Enable the hub, share the link, choose submission types. No DNS, no email, no code. Five minutes.

Setting up the Feedback Hub takes a few clicks. No DNS to configure, no email to wire, no code to write.

Prerequisites

  • You're on Basic or above. The free tier doesn't include the full Hub, see Plans and limits.
  • You're a member of the project you're setting up the hub on.

If you're on Free and want to try inbound feedback collection, the Public bug reporter ships on every tier.

Enabling the hub

From the project, navigate to the Feedback Hub page (gear icon → Feedback hub). Click Enable hub.

Frostbyte generates a unique token-based URL for your project: https://getfrostbyte.dev/feedback/<token>. The token is unguessable; share the URL however you want, pin it in your sidebar, embed it in your support email signature, link to it from your marketing site.

Configuring submission types

The hub supports three submission types. You can toggle each independently:

  • Bugs, defaults on. Form fields: title, description, steps to reproduce, severity.
  • Features, defaults on. Form fields: title, description, why-this-matters.
  • General feedback, defaults on. Free-form body.

If you only want bug reports, turn off the other two; the public portal will only show the active types.

Auto-attach to active release

A toggle on the settings page: Auto-attach accepted items to active release. When on, accepting a submission as a task auto-assigns the new task to the project's current active release. When off, accepted tasks land with no release attached and you assign them later.

Most users leave this on for high-velocity early-stage products and turn it off once the active release is too tightly scoped to take ad-hoc additions.

Public roadmap

Toggle Enable public roadmap to expose /feedback/<token>/roadmap as a public page showing what's planned, in progress, and shipped. See Public roadmap for what's controllable on the roadmap surface.

The settings page shows a one-click Copy link button next to the URL. There's no per-submitter authentication; anyone with the link can submit. This is intentional, friction kills inbound feedback volume.

Disabling the hub

Toggle Disable hub in settings. The public portal returns 404 immediately; existing submissions stay in your moderation queue. Re-enabling reopens the same URL, the token is preserved across enable/disable cycles.

What's next

Last updated