Email Notifications
Reach team members and customers outside the app — comment activity, assignment alerts, status updates, and changelog announcements sent straight to their inbox.
What ProductBridge Emails
ProductBridge can send email for every notification event, plus account lifecycle messages:
| Recipient | Trigger | |
|---|---|---|
| Changelog Announcement | Subscribed end users | A changelog post is published with email notifications enabled |
| Post Assigned / Unassigned | The (un)assigned team member | An admin assigns or unassigns a post |
| Feedback Status Changed | Followers of the post | A feedback post moves to a new status |
| Roadmap Status Changed | Followers of the roadmap item + authors of linked feedback posts | A roadmap item moves to a new status |
| Feedback Linked to Roadmap | Followers of the feedback post | A feedback post is linked to a roadmap item |
| New Comment | Followers of the post | Someone comments on a post they follow |
| Comment Reply | The parent comment's author | Someone replies to their comment |
| Account emails | The individual | Team invitations, member-added confirmations, email verification, password reset |
Delivery for the event-based emails is follower-based (voting on a post auto-follows it) and respects each recipient's Channel preferences.
No email type requires custom SMTP. Everything sends through your custom SMTP when configured, and falls back to the system mailer otherwise — nothing is silently skipped.
Changelog Announcement Emails
The most user-visible email flow. When you publish a changelog post with email notifications enabled, every subscriber on your changelog gets a copy.
How Subscribers Sign Up
End users subscribe directly from the public changelog page on your portal — but only when you've turned on the workspace-level Allow Email Subscriptions toggle in your changelog settings. With that toggle off, the subscribe option is hidden from the public portal entirely.
When someone subscribes, they immediately receive a confirmation email so they know it worked.
Triggering an Announcement
Write a changelog post
Create a new changelog entry in the admin dashboard.
Enable Send Email Notification
On the post editor, toggle Send Email Notification to on. (You can also configure scheduled publishing — the email fires when the scheduled post auto-publishes.)
Publish
ProductBridge queues and sends the email to every subscriber.
Email Format
| Field | Value |
|---|---|
| From | Your organization name + sender email (from your email settings or system default) |
| Subject | {Org Name}: {Post Title} by default — editable as a template |
| Body | Branded HTML with your logo, brand color, featured image, and the rendered changelog content, plus a link back to the public changelog |
| Unsubscribe | Footer note pointing back to your changelog page (no token-based one-click unsubscribe today) |
Unsubscribing
Subscribers manage their subscription from the changelog page on your public portal. There's no token-based unsubscribe link embedded in the email today.
This means if a subscriber wants out, they need to revisit your portal. Consider linking back to your changelog page prominently in the email body so they know where to manage their subscription.
Assignment Emails
When an admin assigns a post to a team member, the assignee gets an email so they know to act — even if they're not currently logged in.
| Field | Value |
|---|---|
| Trigger | Admin assigns or unassigns a post (feedback or roadmap) |
| Recipient | The assignee (or unassigned user) — one email per event |
| Subject | You were assigned to a post / You were unassigned from a post by default |
| Body | Post title with a direct link to the post |
The in-app notification fires alongside the email. Assignees who prefer inbox-only can turn the Email switch off for assignment events in their Channel preferences.
Status Change Emails
When a feedback post or roadmap item moves to a new status, followers of the post get an email (default subject: Status update: {Post Title}). Because voting auto-follows a post, this is how you close the feedback loop — customers who asked for a feature get notified when it ships.
Roadmap status changes additionally email the authors of all feedback posts linked to that roadmap item, with the subject Roadmap update: {Title} is now {New Status}.
Comment Emails
Comment activity is emailed too:
- New comment — followers of the post get
{Actor} commented on "{Post Title}"with an excerpt of the comment - Comment reply — the parent comment's author gets
{Actor} replied to your comment
Recipients can switch comment emails off (and keep in-app only) via Channel preferences.
Email Templates
Every event email's subject and body is an admin-editable template. Go to Settings → Organization → Notifications and open the Email Templates section to customize them per event. Templates support {{placeholder}} tokens — for example {{post_title}}, {{actor_name}}, {{new_status}}, {{post_url}}, and (for changelog) {{organization_name}}, {{post_content}}, {{brand_color}}. The available placeholders are listed alongside each template in the editor.
How ProductBridge Sends Email
Behind the scenes, every email is sent via SMTP using a two-tier resolution:
- Custom org SMTP — if your workspace has Custom SMTP configured and active, it's tried first
- System SMTP fallback — if your custom SMTP fails (or isn't configured), the system mailer is used
This applies to every email type — a misconfigured custom SMTP never blocks delivery.
User-Level Email Preferences
Email delivery is layered:
- Per-user Channel preferences — each team member toggles the Email switch per event from the bell inbox gear icon (see In-App Notifications)
- Workspace-level toggles — e.g., Allow Email Subscriptions for the changelog
- Per-post toggles — e.g., Send Email Notification on a changelog entry
End users unsubscribe from changelog emails via the changelog page on your portal.
What's Not (Yet) Emailed
A few flows you might expect that don't currently send emails:
- New post notifications to admins — new submissions don't email the team
- @ mentions — not implemented
- Moderation alerts — pending content doesn't trigger emails to admins
If any of these would meaningfully change your workflow, let us know.