Show block only if defined permission is not given

1 Initial Problem

At the time being, ILIAS can show a block only if a defined permission is given, e.g. VISIBLE, READ or WRITE. This feature can be used to show specific information to not-logged in users (=ANONYMOUS) or only to logged in users in the public area.

Currently impossible is the following scenario: I would like to show a block with information to those users who are not yet member of a specific course or group. I cannot create a permission reference object for which only a non-member role has READ or VISIBLE permissions. This is not supported by the current RBAC interface.

2 Conceptual Summary

The easiest way to solve this problem would be to extend the list of checked permissions by a fourth option "No Read Permission". This would allow to define a permission reference object within the course or group for which the target group has no read permission.

3 User Interface Modifications

3.1 List of Affected Views

• ILIAS Page Editor » Block

3.2 User Interface Details

• Selection drop-down for "Permission" needs to be extended by new entry "No Read Permission"

3.3 New User Interface Concepts

• None

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Kunkel, Matthias [mkunkel]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: Killing, Alexander [alex]

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• ILIAS-Verein

7 Discussion

Kiegel, Colin [kiegel] 2018-03-05: I think "no write" or "no access" would be also very interesting. Why not two dropdowns?

• [read access] [granted]
• [write access] [denied]
• ...

Kunkel, Matthias [mkunkel], 01 APR 2019 : At the time being, the feature checks against real permissions. "No access given" would be a different pattern. And I am not sure if we need an additional "No 'Edit settings' permission given" condition. You can build the necessary distinction between learners and tutors already with "No Read Permission" by configuring an object in or outside the course (or container) for which the target group does not have READ permission.

And concerning your suggestion of a combined dropdown: this would require a new UI element for constructing conditions that has to be developed first. Such an UI element could be helpful in some scenarios (and substitute the current solution in the survey for routing users depending on their answer). But it does not exist yet. And would like to have already a simple solution for 6.0 that extends the current feature significantly.

JourFixe, ILIAS [jourfixe], 08 APR 2019 : We highly appreciate this suggestion and scheudle it for 6.0.

8 Implementation

Test Cases

Test cases completed at 2019-12-06 by Tödt, Alexandra [atoedt]

• 32094 : Block nur anzeigen, wenn ein Recht NICHT vergeben ist

Approval

Approved at 06 DEC 2019 by Kunkel, Matthias [mkunkel].