Roadmap portal: notifications
This page answers two questions: who wants to hear about which roadmap card, and what did the portal actually send? You reach it via CRM → Roadmap portal → Notifications.
The page is for information only. You cannot send anything from here and you cannot compose a message: there is deliberately no "Send message" button. Emails are only ever created automatically out of your normal work, that is when you move a card, answer a request or update a bug report.
/crm/roadmap-portal/notificationsWhat can I do here?
- In the Subscribers section, see which customer follows which roadmap card and whether they want to hear about status changes, about the release, or both
- Narrow the subscribers down by card, customer, company and kind
- Export the filtered subscriber list as a CSV file, for example for an announcement or an analysis
- In the send log, read every single notification: event, template, language, recipient, time, status and, where applicable, the error text
- Filter the log by event, template, status and recipient, and so check whether a particular message really went out
- Spot a failed send and read the reason in plain language
What you cannot do here: write an email, trigger a send, change a text or create a subscription on a customer's behalf. Subscriptions belong to the customer and are only set in the customer portal. The wording of the emails is maintained under Settings → Email templates.
Step by step
View and export the subscribers of a card
- Open CRM → Roadmap portal → Notifications. The Subscribers section is shown by default.
- Pick the card you are interested in at the top. In addition you can narrow down to a company, a single customer or a kind.
- Each row shows one customer with name, email address, company, the kind of subscription and the date they started following the card.
- Click Export CSV. You get exactly the rows the current filter shows, as a file named
portal-subscriptions.csv. - Open the file in your spreadsheet program. Very large lists are cut off at 10,000 rows; in that case narrow the filter down first.
| Card | Customer | Kind | Language | Subscribed since |
|---|---|---|---|---|
| Collective invoices per period | Sample Trading | Status changes | de | 12 May 2026 |
| Collective invoices per period | Example Shop | Release notice | en | 03 Jun 2026 |
/crm/roadmap-portal/notificationsCheck whether a notification arrived
- Switch to the Send log section.
- Filter by event (for example a card status change) or by recipient.
- Read the Status column: Sent means the email was handed over. Failed means the send did not work; the reason is in the column next to it.
- If it says Skipped, a message for this event and this recipient was already on its way. That is the protection against duplicate sends, not an error.
- If you need the technical delivery details (recipient address, bounce, open time), also look at the general email log.
| Time | Recipient | Event | Kind | Status |
|---|---|---|---|---|
| 17 Aug 2026, 09:02 | anna@example.org | Status changed to "In progress" | Status changes | ✓Sent |
| 17 Aug 2026, 09:02 | max@example.org | Status changed to "In progress" | Status changes | •Skipped |
| 16 Aug 2026, 18:40 | team@example.org | Release 2026.8.2 | Release notice | ×Failed |
/crm/roadmap-portal/notificationsFields explained
Subscribers
| Field | Meaning | Notes/effect |
|---|---|---|
| Card | Roadmap card the customer follows | Only published cards can be followed |
| Customer | Display name of the portal account | The customer maintains it themselves in the portal profile |
| Address the notification goes to | Matches the sign-in address of the portal account | |
| Company | The customer's company from the CRM | Handy as a filter when you want to address a whole company |
| Kind | Status changes or release | See "Values & status"; the two kinds are independent |
| Following since | When the customer started following the card | Newest subscriptions on top |
Send log
| Field | Meaning | Notes/effect |
|---|---|---|
| Event | What triggered the send (sign-in, status change, release, request update, bug update) | Filterable |
| Template | Email template used, e.g. portal_status_change |
Its wording lives under Settings → Email templates |
| Language | Language the email was sent in | Follows the language in the customer's portal profile |
| Recipient | Display name of the portal account that received the message | For data-protection reasons the address itself is only in the email log |
| Subject | The card, request or bug report the message was about | Connects the entry to the triggering item |
| Time | When the send happened | Newest entries on top |
| Status | Sent, Failed or Skipped | See "Values & status" |
| Error | Plain-language reason if the send failed | Only filled for Failed |
Values & status
Subscription kind (portal_subscription_kind)
| Value | Meaning |
|---|---|
| Status changes | The customer gets an email whenever this card's status changes, for example from Planned to In progress. |
| Release | The customer gets exactly one email when the card is released, that is when it moves into the release archive. |
The two kinds are independent: a customer can follow only the release and skip every intermediate step. Without a subscription there is no message, because a subscription is always a deliberate opt-in by the customer.
Status in the send log (portal_notification_status)
| Value | Meaning | What it means for you |
|---|---|---|
| Sent | The email was created and handed over to the mail delivery. | Nothing to do. |
| Failed | The send did not work; the reason is shown next to it. | Check the error text. As soon as the event happens again, the send is retried. |
| Skipped | A message for this event and this recipient already existed. | Not an error, but the built-in protection against duplicate sends. |
Frequently asked questions
Can I send a message to all subscribers from here?
No. The page only shows what happens anyway. If you want to address customers actively, use the CSV export and your usual channel for announcements.
Why is a customer missing from the subscriber list even though they know the card?
Following a card is the customer's own decision. They have to open the card in the portal and switch on Status changes or Release there. You cannot set a subscription for them.
A send failed. Do I have to make up for it?
The error text tells you what went wrong, for example an unreachable address. A new attempt happens automatically with the next event. For persistent failures, check the contact's address and the email log.
Why does the log not show an email address?
For data-protection reasons the log only shows the display name of the portal account. You find the address in the general email log.
Which permission do I need?
Read access to Roadmap Portal (crm:roadmap:read, derived from crm:read). Nothing more is required, because the page does not change anything.