starred/CIPP

Fork 0

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

[GH-ISSUE #3906] [Feature Request]: Edit existing group templates #1748

New issue

Closed

opened 2026-03-02 13:46:45 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:46:45 +03:00

Owner

Originally created by @DBESupport on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3906

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

We want to modify the group settings and dynamic group queries within existing group templates.
It would be great if there was a possibility to edit the JSON directly in a JSON editor or if there will be a new edit button to facilitate the process.
In the earlier version of CIPP it was possible to edit the JSON but unfortunately the save button is gone.

Benefits for MSPs

We use standards to automatically push groups and to ensure that the groups in all tenants are based on the same conditions. If the desired conditions change, we want to avoid having to push a new group with the same name. Instead, we want to modify the existing groups because we use the specific group is mapped to conditional access rules and enterprise applications within our customers tenant. We also want to avoid making changes in standards .

Value or Importance

Consistency and Uniformity – By applying the same standards and conditions for groups across all tenants, you ensure that access rules and security settings remain consistent everywhere. This helps avoid inconsistencies and potential security vulnerabilities.

Efficient Management – If conditions change and you constantly have to create and push new groups with the same name, it can lead to a proliferation of similar groups. This makes it harder to manage and can create confusion for IT administrators.

Maintaining Existing Integrations – The groups are used in Conditional Access rules and Enterprise Applications. If a new group is created instead of modifying an existing one, you may have to manually update all references to the old group in access rules and applications, which is error-prone and time-consuming.

Minimizing Downtime and Risks – By maintaining existing groups and only modifying their conditions, you avoid causing temporary loss of access for users or breaking application functionality due to incorrect configurations.

Automation and Scalability – By using a standard process for pushing and managing groups, it becomes easier to centrally implement changes and apply them consistently across multiple tenants without manual intervention.

In short, adjusting existing groups instead of creating new ones enhances security, efficiency, and manageability of your IT environment.

PowerShell Commands (Optional)

No response

Originally created by @DBESupport on GitHub (Apr 2, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3906 ### 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 We want to modify the group settings and dynamic group queries within existing group templates. It would be great if there was a possibility to edit the JSON directly in a JSON editor or if there will be a new edit button to facilitate the process. In the earlier version of CIPP it was possible to edit the JSON but unfortunately the save button is gone. ### Benefits for MSPs We use standards to automatically push groups and to ensure that the groups in all tenants are based on the same conditions. If the desired conditions change, we want to avoid having to push a new group with the same name. Instead, we want to modify the existing groups because we use the specific group is mapped to conditional access rules and enterprise applications within our customers tenant. We also want to avoid making changes in standards . ### Value or Importance Consistency and Uniformity – By applying the same standards and conditions for groups across all tenants, you ensure that access rules and security settings remain consistent everywhere. This helps avoid inconsistencies and potential security vulnerabilities. Efficient Management – If conditions change and you constantly have to create and push new groups with the same name, it can lead to a proliferation of similar groups. This makes it harder to manage and can create confusion for IT administrators. Maintaining Existing Integrations – The groups are used in Conditional Access rules and Enterprise Applications. If a new group is created instead of modifying an existing one, you may have to manually update all references to the old group in access rules and applications, which is error-prone and time-consuming. Minimizing Downtime and Risks – By maintaining existing groups and only modifying their conditions, you avoid causing temporary loss of access for users or breaking application functionality due to incorrect configurations. Automation and Scalability – By using a standard process for pushing and managing groups, it becomes easier to centrally implement changes and apply them consistently across multiple tenants without manual intervention. In short, adjusting existing groups instead of creating new ones enhances security, efficiency, and manageability of your IT environment. ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:46:45 +03:00

closed this issue
added the
enhancement

no-priority

no-activity

roadmap
labels

kerem commented

2026-03-02 13:46:45 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 12, 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.

@github-actions[bot] commented on GitHub (Apr 12, 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.

kerem commented

2026-03-02 13:46:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 20, 2025):

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

@github-actions[bot] commented on GitHub (Apr 20, 2025): This issue was closed because it has been stalled for 14 days with no activity.

kerem commented

2026-03-02 13:46:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 26, 2025):

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

@github-actions[bot] commented on GitHub (Apr 26, 2025): This issue was closed because it has been stalled for 14 days with no activity.

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

No description provided.

Rows
Columns