Feature Wiki

Information about planned and released features

Tabs

Role Template Screen Revision

1 Requirements

The current role template screen implementation has several issues that should be solved but cannot be regarded as bugfixes, e.g. #8514, #11181, #11182, #11292. These issues might rely on different problems but have all an effect on the current role template screen.

  1. Compared to the usual role administration, role templates use a different table implemantation and a different handling of check/uncheck checkboxes. This should be streamlined and the role template screen should loke similar to the one for roles.

    Permission settings of a role
    Permission settings of a role template
  2. The current role templates cover all repository objects. Also "Roles" and "Organisational Units" have a proper setting block within a template. But permissions for important global features like "Mail" or "Search" are ignored. Therefore it is currently not possible to copy mail or search permissions with a role template. They have to be added manually - which not every administrator might take into consideration.
     
    I recommend to extend the support of role templates to the following components and their permissions:

    • Calendar
    • Mail
    • Privacy and Security
    • Search
    • Statistics and Learning Progress
    • User Management
    All these component settings do not contain only permissions for the administration itself but also for features in the repository or in ILIAS in general. Permissions like "Search: User can use the global search in ILIAS" or "Push Items on the Personal Desktop: User is allowed to push items on the personal desktop of role members" should be supported by role templates, too.

  3. At the time being, role templates show also permissions of components that are either deactivated or no longer available, esp. outdated components like Digilib Books or deinstalled plugins. This is confusing and should be changed.

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: (name, e-mail)
  • 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

...

Last edited: 18. Aug 2022, 07:52, Zenzen, Enrico [ezenzen]