Customize plan notification content and configure the email sender

Dear team,

Summary

Plan notifications currently use fixed content and formatting, and administrators cannot configure the sender identity used for notification emails.

This limits the ability to integrate Plan notifications into customer-specific business processes and can cause email delivery problems in environments with strict email security and anti-spoofing policies.

Current situation

Plan notifications use predefined IBM text and formatting. Customers cannot adapt the wording, subject or branding to match their internal planning processes.

In addition, the sender identity used for Plan notifications cannot be configured by the customer. Depending on the Planning Analytics version and deployment scenario, notifications may be sent using an end-user identity or another platform-defined sender.

In customer environments with strict DMARC, SPF, DKIM or anti-spoofing policies, this can result in notification emails being rejected, quarantined or otherwise not reaching the intended recipient.

This makes Plan notifications difficult to use reliably in production environments.

Requested enhancement

Provide administrative configuration options for the content and sender identity of Plan notification emails.

The function should:

1. Allow notification content to be customized

   • configure the email subject

   • configure the email body

   • optionally include customer-specific branding or formatting

   • retain dynamic information such as plan name, task name, due date and responsible user

   • retain links to the relevant plan or task

2. Allow the sender identity to be configured

   • allow administrators to define the sender address/name used for Plan notifications

   • avoid requiring notifications to be sent as or impersonate the end user

   • support customer email security requirements and existing mail infrastructure

   • allow the customer to use an appropriate organizational mailbox or notification address

Existing per-event notification settings in the plan should remain available.

The configuration should ideally be available centrally by an administrator, rather than requiring every plan owner to configure the sender independently.

Business benefit

Configurable notification content allows customers to integrate Plan notifications into their existing planning and communication processes.

A configurable sender identity improves reliability in production environments where customer mail gateways enforce strict email authentication and anti-spoofing policies.

This makes Plan notifications more suitable for enterprise use and reduces the risk that important workflow notifications are rejected or classified as suspicious emails.

Expected result

Administrators can configure a customer-approved sender identity for Plan notifications.

Plan owners can use notification templates that contain customer-specific wording while still including dynamic plan and task information.

Notifications can therefore be integrated into the customer's existing email and security infrastructure without requiring them to be sent as individual end users.

Out of scope

• No change to when notifications are triggered

• No change to task notification logic or recipient determination

• No change to submit/approve rules

• Slack, Microsoft Teams or other additional notification channels are outside the scope of this request

• Custom notification scheduling is covered separately

With best regards,
Vitalij