starred/CIPP

Fork 0

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

[GH-ISSUE #2917] [Feature Request]: Tenant Groups for standards deployment #1445

New issue

Closed

opened 2026-03-02 13:44:14 +03:00 by kerem · 4 comments

kerem commented

2026-03-02 13:44:14 +03:00

Owner

Originally created by @HappyEarthDay on GitHub (Oct 4, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2917

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

Duplicate of https://github.com/KelvinTegelaar/CIPP/issues/2843, which was closed for the rewrite of the UI

Our MSP services a wide variety of industries with varying needs. For example, the standards we'd like to deploy to our Legal clients differ drastically from those we'd like to deploy to our hospitality clients. The current standards deployment makes it very difficult to deploy standards to subsets of tenants. The All tenants feature and the ability to exclude tenants from the All tenants standard are great, but it doesn't allow us to deploy standards to specific subsets of clients without going into each tenant making the changes, which makes it very difficult to keep track of which settings are applied to tenants.

There are so many amazing features in CIPP that we want to utilize, but we can't deploy most of them to all tenants for whatever reason. For example, we want to deploy the Quarantine Release Request Alert standard to all of the clients that don't have their own IT. However, we don't want to exclude those 20% of our tenants that have internal IT teams from the other standards that we have configured on All Tenants. Having tenant groups would allow us to more accurately deploy standards to our clients based on which category they fall under.

PowerShell commands you would normally use to achieve above request

No response

Originally created by @HappyEarthDay on GitHub (Oct 4, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2917 ### Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole. Duplicate of https://github.com/KelvinTegelaar/CIPP/issues/2843, which was closed for the rewrite of the UI Our MSP services a wide variety of industries with varying needs. For example, the standards we'd like to deploy to our Legal clients differ drastically from those we'd like to deploy to our hospitality clients. The current standards deployment makes it very difficult to deploy standards to subsets of tenants. The All tenants feature and the ability to exclude tenants from the All tenants standard are great, but it doesn't allow us to deploy standards to specific subsets of clients without going into each tenant making the changes, which makes it very difficult to keep track of which settings are applied to tenants. There are so many amazing features in CIPP that we want to utilize, but we can't deploy most of them to all tenants for whatever reason. For example, we want to deploy the Quarantine Release Request Alert standard to all of the clients that don't have their own IT. However, we don't want to exclude those 20% of our tenants that have internal IT teams from the other standards that we have configured on All Tenants. Having tenant groups would allow us to more accurately deploy standards to our clients based on which category they fall under. ### PowerShell commands you would normally use to achieve above request _No response_

kerem

2026-03-02 13:44:14 +03:00

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 13:44:15 +03:00

Author

Owner

@JudgeDreddKLC commented on GitHub (Oct 5, 2024):

Standard grouping would be awesome!

@JudgeDreddKLC commented on GitHub (Oct 5, 2024): Standard grouping would be awesome!

kerem commented

2026-03-02 13:44:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 15, 2024):

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.

@github-actions[bot] commented on GitHub (Oct 15, 2024): 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.

kerem commented

2026-03-02 13:44:15 +03:00

Author

Owner

@JudgeDreddKLC commented on GitHub (Oct 22, 2024):

bumping to make sure it doesn't auto-close!

@JudgeDreddKLC commented on GitHub (Oct 22, 2024): bumping to make sure it doesn't auto-close!

kerem commented

2026-03-02 13:44:15 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Oct 23, 2024):

In Standards v3 the setup of standards changes. This is sort of covered in there.

@KelvinTegelaar commented on GitHub (Oct 23, 2024): In Standards v3 the setup of standards changes. This is sort of covered in there.

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

No description provided.

Rows
Columns