Permission inheritance: Delete local policies separately

1 Description

Up to now, the local policies of a role can be either kept or deleted when the permission settings of the role are saved with active permission inheritance ("Change existing objects"). However, this can only be done across the board, i.e., when local policies are deleted, all of them (below the edited node) will be deleted afterwards.

This way, administrators either have to have a really good overview of the permission policies in the Repository or to disregard possible "collateral damage".
Particularly with big organizations mapped in ILIAS that may use independently acting local administrators, this is a problem.

Therefore, a possibility should be created to deleted local policies separately when saving a role with active permission inheritance.

The function could look like this:

• When saving a role with active permission inheritance, the familiar intermediate screen Settings for "Change Existing Objects" appears.
• In case the user chooses the Delete Local Policies option, an overview of the Repository is displayed below that lists any container object in the Repository but offers a clickable checkbox only for those containers that feature a local permission policy for the edited role:

2 Status

• Scheduled for Release: Not scheduled yet
• Funding: Required
• Development: Feature is to be developed by tbd

3 Additional Information

• If you want to know more about this feature, its implementation or funding, please contact: Florian Suittenpointner / suittenpointner (at) qualitus.de

4 Discussion

Zenzen, Enrico [ezenzen], 18 AUG 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

5 Follow-up