Web Portal
Add the hosted Gleam Portal to a web product with a direct link, iframe embed, or sidebar launcher.
Last reviewed June 2, 2026
Portal URL Shape
Every project has a hosted Portal. Projects can use a path route on the main app domain or a configured subdomain route.
| Mode | Example |
|---|---|
| Path route | https://app.gleam.land/p/{projectPathId}/feedback |
| Subdomain route | https://{portalSubdomain}.gleam.land/feedback |
| Announcement detail | https://{portal}/announcement/{announcementId} |
| Post detail | https://{portal}/post/{postId} |
Choose The Embed Mode
Start with the least complex surface that still fits the product experience. A direct link is easiest to maintain and debug. An iframe is useful when the Portal should appear inside an existing help or account page. A sidebar launcher is best when users should keep their current product context while sending feedback.
The Portal is still hosted by Gleam in each mode, so your app does not need to reimplement feedback lists, voting, roadmap stages, announcement detail pages, or request detail routes.
If your app has strict security headers, test the embed path in the same environment where users will run it. Iframes are sensitive to frame policy, sandbox settings, referrer policy, cookie behavior, and mobile viewport sizing.
For most teams, the launch sequence should be direct link first, sidebar or iframe second, and custom native UI only after the product has enough feedback volume to justify maintaining a separate surface.
| Mode | Best for | Implementation note |
|---|---|---|
| Direct link | Fast launches, docs sites, account settings, mobile web, and low-maintenance support links. | Use target=_blank with rel=noopener noreferrer when leaving your app shell. |
| Iframe | Product pages where feedback should appear inline and the surrounding navigation should remain visible. | Give the frame enough height, a clear title, and a tested fallback link for browsers or policies that block embeds. |
| Sidebar launcher | Apps where users should keep their current workflow visible while opening feedback or roadmap context. | Manage focus, close behavior, and route changes in your app; the iframe still loads the hosted Portal URL. |
Recommended Direct Link
Start with a normal link. It is reliable, fast to test, and works across browsers without iframe policy surprises.
Feedback link
<a
href="https://app.gleam.land/p/YOUR_PROJECT_SLUG/feedback"
target="_blank"
rel="noopener noreferrer"
>
Send feedback
</a>Iframe Embed
Use an iframe when the Portal should sit inside an existing product page. Keep the frame tall enough for feedback lists and detail pages.
Inline iframe
<iframe
src="https://app.gleam.land/p/YOUR_PROJECT_SLUG/feedback"
title="Gleam feedback portal"
loading="lazy"
referrerpolicy="strict-origin-when-cross-origin"
style="width:100%;min-height:640px;border:0;border-radius:12px"
></iframe>