Private previewWorkspaces are by invitation

HeedPost

01Collect

Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.

02Understand

Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.

03Ship and tell

Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.

04Run it

Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.

05Connect

Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.
AIDocsHelpPricingBlog

Collect

Understand

Ship and tell

Run it

Connect

Request an inviteSign in

Help centreWidget and identity

Sign customers in with single sign-on

Your app signs a short token saying who somebody is, and HeedPost starts their session. No SAML, no metadata.

Who Admins and developersPlan Plus and Pro

Set it up

  1. Turn it on in Settings › Sign-in and privacyUnder Single sign-on. You get a signing secret.
  2. Sign a token on your serverA JWT signed with HS256, carrying sub, email, iat and exp. Make it when someone clicks through.
  3. Send them inTo /auth/sso?token=… on your workspace, or give the same token to the widget.
  4. Require it, if you wantEmailed links and Google then stop working, and people are sent to a start URL in your app.

Everything rests on the secret. Keep it on your server. Rotating it takes effect at once, and every token signed with the old one stops working.

The details

The claims, the two-minute window, what each error means, and code in Python and Node are in the single sign-on guide.

Related

Did this answer it?