mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #4041] [Feature Request]: Group-Based OneDrive Shortcut Automation in CIPP #1826
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#1826
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 @wijzijnmerlin on GitHub (May 4, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4041
Please confirm:
Problem Statement
Currently, CIPP allows adding OneDrive shortcuts to individual users or multiple users through bulk actions. However, this process requires manually assigning shortcuts for each user, which is time-consuming and error-prone. Users with similar roles (e.g., within the same department or function) typically require identical SharePoint/OneDrive access. For example, colleagues in the same role often need the same set of OneDrive shortcuts, and manually configuring these for each user increases the risk of mistakes, such as forgetting to add a critical shortcut.
Benefits for MSPs
Value or Importance
This feature would allow MSPs to automate shortcut assignments when a user is added to a group, integrating seamlessly with CIPP’s existing workflows like “Copy Groups From.” Also, onboarding a new employee in a client’s department could involve adding them to a group, automatically applying predefined shortcuts to that's groups assets.
PowerShell Commands (Optional)
No response
@github-actions[bot] commented on GitHub (May 14, 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 (May 19, 2025):
This issue was closed because it has been stalled for 14 days with no activity.