starred/CIPP

Fork 0

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

[GH-ISSUE #4536] [Feature Request]: when client is not in CIPP we want the ability to create a custom alert where we type in the domain, so it alerts on us a password breach. #2090

New issue

Closed

opened 2026-03-02 13:49:32 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:49:32 +03:00

Owner

Originally created by @alexpostiglionecoreitech on GitHub (Aug 18, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4536

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

client is not in CIPP so we want the ability to create a custom alert where we type in the domain, so it alerts on us a breach. Running data breach manually works

Benefits for MSPs

helps for security

Value or Importance

security

PowerShell Commands (Optional)

No response

Originally created by @alexpostiglionecoreitech on GitHub (Aug 18, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4536 ### 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 client is not in CIPP so we want the ability to create a custom alert where we type in the domain, so it alerts on us a breach. Running data breach manually works ### Benefits for MSPs helps for security ### Value or Importance security ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:49:32 +03:00

closed this issue
added the
enhancement

no-priority

not-assigned
labels

kerem commented

2026-03-02 13:49:33 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 18, 2025):

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

@github-actions[bot] commented on GitHub (Aug 18, 2025): Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, **feature requests are limited to paying users**. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "**I’d like to work on this!**" to assign the issue to yourself. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. _Thank you for understanding,_ **The CIPP Team**

kerem commented

2026-03-02 13:49:33 +03:00

Author

Owner

@JohnDuprey commented on GitHub (Aug 18, 2025):

Verified sponsor

@JohnDuprey commented on GitHub (Aug 18, 2025): Verified sponsor

kerem commented

2026-03-02 13:49:33 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Aug 22, 2025):

We've discussed this with the dev team - This is out of scope, the work we'd have to implement would be a really big lift and big changes to how CIPP works. If you want them in CIPP, add them to a tenant.

@KelvinTegelaar commented on GitHub (Aug 22, 2025): We've discussed this with the dev team - This is out of scope, the work we'd have to implement would be a really big lift and big changes to how CIPP works. If you want them in CIPP, add them to a tenant.

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

No description provided.

Rows
Columns