starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #4263] [Feature Request]: Multiple notification end points #1929

New issue

Closed

opened 2026-03-02 13:48:16 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:48:16 +03:00

Owner

Originally created by @TMGCL-TS on GitHub (Jun 12, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4263

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

Adding an option to add alternate notification types for different alerts.
EG Errors go to xyz email while HIBP alerts go to ABC email,

Benefits for MSPs

Ability to filter different alert types to different endpoints for different teams to respond to.
EG CIPP alerts need to go to the CIPP team to review, where as alerts need to go to our support team to process.
But high priority alerts, such as HIBP alerts or mailflow rule changes should go to a high priority email for instant review from the team

Value or Importance

Nice to have as it allows filtering of alerts easier
However would allow us to then use the alerting more then we currently are as we don't need to flood the support queue with nonsense alerts

PowerShell Commands (Optional)

No response

Originally created by @TMGCL-TS on GitHub (Jun 12, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4263 ### 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 Adding an option to add alternate notification types for different alerts. EG Errors go to xyz email while HIBP alerts go to ABC email, ### Benefits for MSPs Ability to filter different alert types to different endpoints for different teams to respond to. EG CIPP alerts need to go to the CIPP team to review, where as alerts need to go to our support team to process. But high priority alerts, such as HIBP alerts or mailflow rule changes should go to a high priority email for instant review from the team ### Value or Importance Nice to have as it allows filtering of alerts easier However would allow us to then use the alerting more then we currently are as we don't need to flood the support queue with nonsense alerts ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:48:16 +03:00

closed this issue
added the
enhancement

no-priority

not-assigned
labels

kerem commented

2026-03-02 13:48:17 +03:00

Author

Owner

@TMGCL-TS commented on GitHub (Jun 12, 2025):

I can try make a POC if there is no indication of this being worked on any time soon by the team.

@TMGCL-TS commented on GitHub (Jun 12, 2025): I can try make a POC if there is no indication of this being worked on any time soon by the team.

kerem commented

2026-03-02 13:48:17 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jun 13, 2025):

We're not implementing this due to a couple of reasons; people will start using this to directly send emails to clients which is what we want to prevent, also we recommend using our webhook engine to have something else process it, e.g. PowerAutomate, Tines, Zapier, etc.

@KelvinTegelaar commented on GitHub (Jun 13, 2025): We're not implementing this due to a couple of reasons; people will start using this to directly send emails to clients which is what we want to prevent, also we recommend using our webhook engine to have something else process it, e.g. PowerAutomate, Tines, Zapier, etc.

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#1929

No description provided.

Rows
Columns