End Users
Every customer who submits feedback, votes, comments, or reacts is an End User in ProductBridge — with their own profile, history, and segment membership.
End Users vs. Team Members
ProductBridge has two distinct user types:
| Type | Who They Are | Where They Sign In |
|---|---|---|
| Team Members | Your internal team — PMs, engineers, support | Admin dashboard |
| End Users | Your customers and prospects | Public portal |
This page is about end users — the people on the other side of your portal. For team members and roles, see Members & Roles.
How End Users Get Created
End users land in ProductBridge through three channels:
- Public portal sign-up — they create an account directly when submitting feedback or voting
- Identity verification from your app — you sign a JWT in your app and pass it to the ProductBridge widget, which creates or matches the user automatically
- Integration sync — when feedback arrives from Intercom, Slack, Zendesk, etc., the original sender is mapped to an end user via integration identity (
slack:U12345,intercom:abc, etc.)
All three paths converge on the same user record, so a customer who emails you on Intercom, votes on your public portal, and signs in via your app shows up as one end user — not three.
Signed-In vs. Anonymous Visitors
Signing in is required to participate. Anonymous visitors can browse public boards, but every write action requires an account:
| Action | Anonymous Visitor | Signed-In End User |
|---|---|---|
| Browse public boards and posts | Yes | Yes |
| Submit a post | No — prompted to sign in | Yes |
| Vote | No — prompted to sign in | Yes |
| Comment | No — prompted to sign in | Yes |
| React | No — prompted to sign in | Yes |
The same rule applies in the widget: anonymous feedback is not supported, so widget submissions come from identified users.
If your product already has authenticated users, set up identity verification so every widget interaction is identified automatically — your customers never see a second sign-in.
End User Profile
Every end user has:
| Field | Source |
|---|---|
| Required, globally unique | |
| Name | Provided by user or pulled from integration |
| Avatar | Uploaded or pulled from integration |
| Company info | Company name, MRR, customer status, renewal risk, renewal date |
| Joined | When the user was first created |
| Activity counts | Posts, comments, and upvotes |
Click any end user on the Users page to see their profile and engagement.
Identifying Users in the Widget
If you're using the ProductBridge widget, you can tell ProductBridge who the current signed-in user is so their feedback is attributed correctly.
Identification uses a signed JWT: your server signs a token that proves the user is who they claim, and you pass it to the widget as userToken. There is no unsigned "plain identity" mode — every identify call is verified against your widget secret.
See Identity Verification for the full setup.
External User Resolution
When feedback arrives from a third-party integration, ProductBridge matches the sender against existing end users:
- By external ID — if a Slack user
U12345posted feedback before, the new post is linked to the same end user. - By email — if the integration provides an email and that email matches an existing end user, they're linked.
- By creation — if no match, a new end user is created with the integration's identity attached.
This is what lets you see "Sarah from Acme submitted 3 posts via Intercom, voted on 5 posts on the portal, and commented on the Slack #feedback channel" — all as one unified profile.
Hiding User Identity
If your organization has Hide user identities enabled, end users are still tracked internally with full profile data — but their names and avatars are replaced with random ones on the public portal.
This is public-facing only. Your admin dashboard still shows who submitted what, so you can follow up privately.
Grouping End Users with Segments
Once you have end users, the natural next step is grouping them:
- Enterprise — users where company MRR is greater than $5k
- At-risk accounts — users where renewal risk is High
- Acme team — users whose email contains
@acme.com
These groups are called User Segments. Segments power audience gating (which boards can a user see?) and filtering on the Users page.
Privacy & Data
- End user data is scoped to your organization — no other workspace can see it.
- Email is always required for an end user to exist. Even integration-sourced users need an email tied to their external ID.
- Need to delete an end user's data for a GDPR or similar request? There's no self-serve delete in the dashboard today — contact support and they'll process the removal.