starred/CIPP

Fork 0

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

[GH-ISSUE #2982] [Feature Request]: #1482

New issue

Closed

opened 2026-03-02 13:44:34 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @brianman108 on GitHub (Nov 13, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2982

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.

Looking for a custom role or other means to scope permissions to change global admin users account password but still be able to reset normal users. The goal is to allow our helpdesk to use CIPP without giving them the ability reset our client's GA's

PowerShell commands you would normally use to achieve above request

No response

Originally created by @brianman108 on GitHub (Nov 13, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2982 ### 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. Looking for a custom role or other means to scope permissions to change global admin users account password but still be able to reset normal users. The goal is to allow our helpdesk to use CIPP without giving them the ability reset our client's GA's ### PowerShell commands you would normally use to achieve above request _No response_

kerem

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

closed this issue
added the
enhancement

no-priority
labels

kerem commented

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

Author

Owner

@KelvinTegelaar commented on GitHub (Nov 13, 2024):

Hello,

Thank you for reaching out! This report has been classified as a support request rather than a bug report. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support.

Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions, where you may find answers to similar queries.

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

Thank you for your understanding,
The CIPP Team

@KelvinTegelaar commented on GitHub (Nov 13, 2024): Hello, Thank you for reaching out! This report has been classified as a support request rather than a bug report. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support. Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions, where you may find answers to similar queries. Did you get this notification in error? Reply with a screenshot of your sponsorship payment, and we’ll gladly reopen the request. Thank you for your understanding, The CIPP Team

kerem commented

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

Author

Owner

@brianman108 commented on GitHub (Nov 13, 2024):

I am now a sponser and i made this based off of a support ticket where the support agent recommended i submit the feature request.

@brianman108 commented on GitHub (Nov 13, 2024): I am now a sponser and i made this based off of a support ticket where the support agent recommended i submit the feature request.

kerem commented

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

Author

Owner

@brianman108 commented on GitHub (Nov 13, 2024):

Hello,

Thank you for reaching out! This report has been classified as a support request rather than a bug report. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support.

Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions, where you may find answers to similar queries.

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

Thank you for your understanding, The CIPP Team

@brianman108 commented on GitHub (Nov 13, 2024): > Hello, > > Thank you for reaching out! This report has been classified as a support request rather than a bug report. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support. > > Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions, where you may find answers to similar queries. > > Did you get this notification in error? Reply with a screenshot of your sponsorship payment, and we’ll gladly reopen the request. > > Thank you for your understanding, The CIPP Team ![image](https://github.com/user-attachments/assets/4884f937-61f5-4a0f-8fd7-1d621c53e6dc)

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

No description provided.

Rows
Columns