mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #4931] [Feature Request]: Ability to perform Group Nesting #2323
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#2323
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mweber1980 on GitHub (Nov 9, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4931
Please confirm:
Problem Statement
We work with persona's, and this means we create a group for a persona and create groups per resource so that when a user is added to a group, that user has access to the resource by a groups. This way of working will provide standarization for MSP's.
Currently CIPP does not have a feature to add groups to a group (only individual users)
Benefits for MSPs
for an MSP this will have banefits of using a standard way of using group nesting to ease management on resource access management for example.
Value or Importance
Important, because now we have to switch to Microsoft portals, because cipp does not support these feature and created additional management overhead.
PowerShell Commands (Optional)
No response
@github-actions[bot] commented on GitHub (Nov 9, 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
@mweber1980 commented on GitHub (Nov 11, 2025):
Currently we have the following structure.
Role-Werkplaats
Data-Werkplaats-RW
Data-Machine-RW
We want to aad Role-Werkplaats-RW group into Data-Werkplaats-RW
Within CIPP we do not have the ability to select a group to add as member.
@github-actions[bot] commented on GitHub (Nov 21, 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 (Nov 26, 2025):
This issue was closed because it has been stalled for 14 days with no activity.