[GH-ISSUE #4842] [Feature Request]: Multiple Email Targets for Alert Notifications #2262

Closed
opened 2026-03-02 13:50:55 +03:00 by kerem · 5 comments
Owner

Originally created by @HappyEarthDay on GitHub (Oct 17, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4842

Please confirm:

  • I have searched existing feature requests (open and closed) and found no duplicates.
  • **me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

Currently, CIPP only allows a single global email address to receive alert notifications, as configured in the Settings > Notifications page. This limitation prevents teams from routing alerts to the appropriate departments. For example, security-related alerts should go to security@mspdomain.com, while support-related alerts should be sent to support@mspdomain.com. Managing this through inbox rules or mail forwarding has proven unreliable and difficult to maintain.

Benefits for MSPs

Allowing multiple configurable email destinations per alert type would enable MSPs to route alerts directly to the correct teams. This would streamline operations, ensure faster response times, and reduce noise in shared mailboxes. Additionally, having the option to set custom or pre-defined addresses within the Alert Configuration page would eliminate the need for complex mail filtering rules.

Value or Importance

This enhancement would significantly improve alert management scalability and accuracy across multiple teams. It ensures that actionable alerts reach the correct stakeholders immediately, supporting better security posture, faster issue resolution, and improved operational efficiency.

Thank you to the CIPP team for helping the MSP community.

PowerShell Commands (Optional)

No response

Originally created by @HappyEarthDay on GitHub (Oct 17, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4842 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement Currently, CIPP only allows a single global email address to receive alert notifications, as configured in the Settings > Notifications page. This limitation prevents teams from routing alerts to the appropriate departments. For example, security-related alerts should go to security@mspdomain.com, while support-related alerts should be sent to support@mspdomain.com. Managing this through inbox rules or mail forwarding has proven unreliable and difficult to maintain. ### Benefits for MSPs Allowing multiple configurable email destinations per alert type would enable MSPs to route alerts directly to the correct teams. This would streamline operations, ensure faster response times, and reduce noise in shared mailboxes. Additionally, having the option to set custom or pre-defined addresses within the Alert Configuration page would eliminate the need for complex mail filtering rules. ### Value or Importance This enhancement would significantly improve alert management scalability and accuracy across multiple teams. It ensures that actionable alerts reach the correct stakeholders immediately, supporting better security posture, faster issue resolution, and improved operational efficiency. Thank you to the CIPP team for helping the MSP community. ### PowerShell Commands (Optional) _No response_
Author
Owner

@HappyEarthDay commented on GitHub (Oct 17, 2025):

On the Settings < Notifications page, I'd love to have a section for "Additional alert email addresses" and have those show up as options when configuring individual alerts.

<!-- gh-comment-id:3416443542 --> @HappyEarthDay commented on GitHub (Oct 17, 2025): On the Settings < Notifications page, I'd love to have a section for "Additional alert email addresses" and have those show up as options when configuring individual alerts.
Author
Owner

@HappyEarthDay commented on GitHub (Oct 20, 2025):

I realized I would love to add multiple tarkets for webhooks too!

<!-- gh-comment-id:3422469461 --> @HappyEarthDay commented on GitHub (Oct 20, 2025): I realized I would love to add multiple tarkets for webhooks too!
Author
Owner

@mweber1980 commented on GitHub (Oct 22, 2025):

+1

<!-- gh-comment-id:3433793047 --> @mweber1980 commented on GitHub (Oct 22, 2025): +1
Author
Owner

@github-actions[bot] commented on GitHub (Nov 1, 2025):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

<!-- gh-comment-id:3475453070 --> @github-actions[bot] commented on GitHub (Nov 1, 2025): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 7, 2025):

This issue was closed because it has been stalled for 14 days with no activity.

<!-- gh-comment-id:3500173046 --> @github-actions[bot] commented on GitHub (Nov 7, 2025): This issue was closed because it has been stalled for 14 days with no activity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#2262
No description provided.