starred/CIPP

Fork 0

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

[GH-ISSUE #3900] [Feature Request]: Add ViewPrivateItems permission to calendar permission settings with Exchange mailbox management. #1741

New issue

Closed

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

kerem commented

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

Owner

Originally created by @leanderthanx on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3900

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

Feature would eliminate need to grant this permission with Exchange Online Powershell and/or Outlook on the web

https://techlabs.blog/categories/office-365/office-365-allow-delegates-view-private-items-shared-mailbox-using-powershell

Benefits for MSPs

Feature would eliminate need to grant this permission with Exchange Online Powershell and/or Outlook on the web, which reduces manual work.

https://techlabs.blog/categories/office-365/office-365-allow-delegates-view-private-items-shared-mailbox-using-powershell

Value or Importance

Feature would eliminate need to grant this permission with Exchange Online Powershell and/or Outlook on the web

PowerShell Commands (Optional)

Add-MailboxFolderPermission -Identity sharedmailbox@yourdomain.com:\Calendar -User user@yourdomain.com -AccessRights Editor -SharingPermissionFlags Delegate,CanViewPrivateItems

Originally created by @leanderthanx on GitHub (Mar 31, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3900 ### 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 Feature would eliminate need to grant this permission with Exchange Online Powershell and/or Outlook on the web https://techlabs.blog/categories/office-365/office-365-allow-delegates-view-private-items-shared-mailbox-using-powershell ### Benefits for MSPs Feature would eliminate need to grant this permission with Exchange Online Powershell and/or Outlook on the web, which reduces manual work. https://techlabs.blog/categories/office-365/office-365-allow-delegates-view-private-items-shared-mailbox-using-powershell ### Value or Importance Feature would eliminate need to grant this permission with Exchange Online Powershell and/or Outlook on the web ### PowerShell Commands (Optional) Add-MailboxFolderPermission -Identity sharedmailbox@yourdomain.com:\Calendar -User user@yourdomain.com -AccessRights Editor -SharingPermissionFlags Delegate,CanViewPrivateItems

kerem

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

closed this issue
added the
enhancement

no-priority

no-activity
labels

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Apr 10, 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 10, 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:43 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 14, 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 (Apr 14, 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:46:43 +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 referenced this issue

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

[PR #1741] [MERGED] Fixed a missed function rename for Halo #3391

kerem referenced this issue

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

[PR #1765] [MERGED] Dev to release #3403

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

No description provided.

Rows
Columns