We love to hear your feedback. Your suggestions and ideas are important to us. Our feedback forum is a great place to post your ideas and vote on others. Please share your detailed use case and how the proposed enhancements can increase value to your business. We do read all of your posts, but may not be able to respond to all comments.
More information on the status of submitted ideas can be found here
Have a permission set that clearly allows you to turn on or off the ability to remove core items or non-core items from development plans. For example, "Can remove items assigned as core" and "Can remove non-core items from development plans." This would ensure super-users or other users can remove core learning activities if this permission is on. This would also ensure the second permission set could be switched on for managers, for example, to remove non-core items from their direct reports' development plans.
|
What business value are you trying to achieve?
When managing the learning library, our compliance requires users not to be able to remove core activities from development plans by anyone but super-users. Currently, the permissions set that allow a user to remove or delete a learning activity from a development plan (assigned as core or not) are related to being able to view another user's development plan. For example, the permission " Manage learning library" or from employee search "Access employee development inside or outside of team". We need to turn off these permissions to prevent users from removing a module from another user's development plan. However, these permissions are also used for other purposes, such as admin staff viewing and updating development plans or managers removing non-core items from direct reports' development plans. |
