starred/CIPP

Fork 0

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

[GH-ISSUE #3737] FEATURE REQUEST: remove from groups in Edit User page #1655

New issue

Closed

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

kerem commented

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

Owner

Originally created by @isgq-github01 on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3737

Thank you so much for adding/returning the ability to add to multiple groups from the Edit User page. Would it be possible to also add the ability to remove users from groups (multiple groups at once as well) on the same page? If it would be possible for the box to be populated with their existing group memberships that would be even better.

Worth noting that the View User page does populate with group memberships, and there is a Bulk Actions button in the top right corner, but the button does not appear to do anything at present. The action menu for each group just has a link to Edit Group.

Originally created by @isgq-github01 on GitHub (Mar 5, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3737 Thank you so much for adding/returning the ability to add to multiple groups from the Edit User page. Would it be possible to also add the ability to remove users from groups (multiple groups at once as well) on the same page? If it would be possible for the box to be populated with their existing group memberships that would be even better. Worth noting that the View User page does populate with group memberships, and there is a Bulk Actions button in the top right corner, but the button does not appear to do anything at present. The action menu for each group just has a link to Edit Group.

kerem

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

closed this issue
added the
enhancement

no-priority

no-activity
labels

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Mar 5, 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 (Mar 5, 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:45:59 +03:00

Author

Owner

@isgq-github01 commented on GitHub (Mar 9, 2025):

Not sure why the sponsorship wasn't detected but we're definitely a sponsor!

@isgq-github01 commented on GitHub (Mar 9, 2025): Not sure why the sponsorship wasn't detected but we're definitely a sponsor! ![Image](https://github.com/user-attachments/assets/a1cd7b08-68e6-4890-949f-4be2aa54a259)

kerem commented

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

Author

Owner

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

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

No description provided.

Rows
Columns