The feedback portal is the public face of your roadmap and changelog. It works out of the box on a Gleap address; the settings below make it look and behave like part of your product.
Everything here is under Feedback portal → Settings.
General settings gives you two ways to publish. Standalone is a link you share. Embedded gives you an iframe snippet for a page of your own site — and you can embed the whole portal or just one part of it: the feature list, the roadmap, or the changelog.
Embedding one part is how most teams do it: a “What's new” page carrying only the changelog reads far better than a full portal squeezed into a marketing site.
Add a domain like feedback.yourdomain.com and point it at Gleap with the DNS record the page shows you. The status is displayed while it's being verified, so you can see whether the record has propagated rather than guessing.
It's worth doing. A portal on your own domain reads as your product; one on someone else's reads as a third-party tool, and people are more cautious about signing in to it.
Under SEO & customization you set a header logo, a favicon, and the URL the logo links to — point it back at your main site, so the portal isn't a dead end. You can also add navigation links across the top.
Colours aren't set here: the portal uses the same colours as your widget, so branding stays in one place.
Gleap generates static pages for the portal, and the same screen links to its sitemap so you can hand it to a search console.
There's a field for custom code too — analytics, or whatever else you run on your own pages.
The Security page controls five things independently, each set to Everyone, Identified users, or Nobody:
view public comments,
submit public comments,
upvote feature requests,
submit feature requests,
subscribe to changelogs.
“Identified users” is the setting that keeps a portal usable: anyone can read, only signed-in customers can post or vote. Open submission on a public portal collects spam — the tighter setting costs you almost no real feedback.
Whatever you choose, updates from your team stay publicly visible, and you can still notify everyone who upvoted.
The same page can enforce login for the whole portal and take a login redirect URL — your own sign-in page. Enforcing login turns a public roadmap into a customers-only one, which is the right shape when your roadmap says more about your plans than you want in public.
General settings also picks the email template used for changelog comment notifications, so those messages look like the rest of your email.
