userGist Docs

Link customers to your published Customer Portal, or use the SDK request board inside your product. This guide keeps its earlier URL so existing documentation links continue to work.

1. Set up the destination

Open Configure → Portal settings, choose your company address, include the app, save, and publish the portal. Publish the requests and content customers should see. Follow Portal setup for address rules, branding, and previews.

The portal uses a company subdomain and app path, such as https://acme.usergist.com/mobile/roadmap. Use the address shown in Portal settings, rather than the earlier roadmap.usergist.com/<slug> pattern.

2. Link from your website

Add a normal link to the roadmap, requests, help center, or changelog:

<a href="https://acme.usergist.com/mobile/roadmap">See our roadmap</a>
<a href="https://acme.usergist.com/mobile/requests">Suggest a feature</a>
<a href="https://acme.usergist.com/mobile/help">Find help</a>
<a href="https://acme.usergist.com/mobile/changelog">Read product updates</a>

Public reading needs no sign-in. Submitting an idea or voting starts the portal's email verification and feedback-consent flow. That identity is separate from your SDK user session.

Iframe embedding is not implemented

The current hosted portal sends X-Frame-Options: DENY and has no ?embed=1 mode. Use a normal link. The earlier iframe, ?theme=dark, and comma-separated status-filter instructions do not describe the current portal.

3. Show the request board inside your app

The SDK's request board is a separate in-product surface using the same app's request data. It supports anonymous and identified SDK users, subject authentication, and feedback consent.

For React Native:

UserGist.openRequestsBoard()
UserGist.openRequestDetail('REQUEST_ID')

Use the platform-specific guides for React Native, iOS, Android, Flutter, or Web. A portal request can be private in the SDK, and an SDK request can be private on the portal: each surface applies its own access rules.

4. Build a custom read-only view

Use the current Customer Portal API for published request reads and Portal content API for roadmap items, release notes, and help articles. Do not put a dashboard token or backend server key into a public website.

The earlier /v1/public/roadmap/:slug API remains a request-only surface controlled by its older settings. It does not return the complete company portal.

5. Close the loop

Update request status and the team response as work progresses. Link related requests to team roadmap items, then create a changelog entry for shipped work. Request follower rules queue in-app SDK instructions; automatic request-update push is not implemented. Create broader in-app announcements or native push campaigns separately under Engage.