Show Advanced KnowledgeHide Advanced Knowledge

OrgUnit behaves in RBAC like a group and category

1 Requirements

The OrgUnit shows up in the repository/personal desktop rbac in a way to:

1. Offer the same local administration capability as a category does now
2. Be selectable for sharing between peers

1.1 The current situation

The orgunit works fine and is perfect in the administration but not in the repository and the personal desktop. The features lacking are there, just not for the orgunit.

1. If I manage the orgunit not as an orgunit but as a category I can set up local administration so the supervisor can in all of the repository see and manage his own people and NOT SEE other supervisors people.
2. If I manage the orgunit not as an orgunit but as a group I an employee can on the personal desktop share objects with his peers.

This means to have full functionality of the orgunit in ILIAS at the moment I need to clone it as a category and a group and have to keep the three synced. This is tedious and error prone.

When you implement this might be two seperate features but for discussion I think they should be together.

2 Status

• Scheduled for: Not scheduled yet (will be set by Jour Fixe)
• Funding: Required / Interest in funding: (please indicate if you are interested to fund this feature)
• Maintainer: (will be set by Jour Fixe)
• Implementation of the feature is done by (company, developer)
• Contract settled: No | Fill in "Yes" if a contract is already settled and add Institution / Organisation in "Funding" row
  
• Tested by / status: (name, e-mail), (status information set after implementation)

3 Additional Information

Contact the following persons if you want to know more about this feature, its implementation or funding:

• Information about concept: (Markus Graf, markusalbertgraf@gmail.com)
• Information about funding: (name, e-mail)
• Information about implementation: (name, e-mail)

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 Implementation

...