Learning Sequence: Streamlining of Permission Handling

1 Initial Problem

The current handling of JOIN und LEAVE permissions in the Learning Sequence object is different from other objects in ILIAS like course or group. This leads to problems and wrong configurations and should be changed.

The permissions JOIN and LEAVE have been introduced with the container objects 'Group' and 'Course' to handle the self-registration of users for these object types. The default permission setting for users that are not members yet is to give them VISIBLE and JOIN to see a course/group in the object lists of the repository and to register by themselves to such a course/group (assumed self-registration is allowed). This is why non-members usually do not have READ permission for these objects. They get this permission only by becoming a course or group member.

The object type 'Learning Sequence' in its current implementation behaves a bit different. It uses the JOIN permission to start a learning sequence and the LEAVE permission to finish/complete its use (and to be removed from the list of members). READ permission for the learning sequence gives the opportunity to "look into the object" and even see the linear workflow listing of the embedded objects. But users get no access to the content of learning sequence even if they have READ permission for the embedded objects – as this is only granted by JOIN permission. While JOIN has usually a lower position in the hierarchy of ILIAS permissions than READ, in the learning sequence it is vice versa.

2 Conceptual Summary

The original feature request came with two options to solve the problem and to make the learning sequence behave like other container objects in ILIAS:

1. Migrate the current permissions JOIN and LEAVE to new permissions.
2. Remove the permissions at all and allow starting the learning sequence with READ permission.

In the meantime, I highly recommend to make things easier and to drop these special permissions.

Suggestion : Remove the permissions at all and allow starting the learning sequence with READ permission

Preferred option is to get rid of this confusing permission handling and to remove these permissions at all.

• The actions of looking into a learning sequence, starting and finishing were all controlled by READ permission.
• If users have READ permission for a learning sequence they can start it.
• If access to the learning sequence should be controlled manually, the user or member role of the parent object should only grant VISIBLE permission and a tutor or admin has to add users manually to the participant list of a learning sequence.

The Learning Sequence would behave similar to the Exercise object where also no specific permission to join or leave the exercise has been implemented.

3 User Interface Modifications

3.1 List of Affected Views

No user interfaces are affected by this change of permission handling.

3.2 User Interface Details

None

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 Privacy Information

None

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Kunkel, Matthias [mkunkel]
• Maintainer: Klees, Richard [rklees]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

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

• ILIAS-Verein

9 Discussion

Kunkel, Matthias [mkunkel], 15 MAR 2023: I would like to fix the permission confusion in the Learning Sequence with ILIAS 9. This is why I have updated this feature request. My preference now is to get rid of the two permissions JOIN and LEAVE and to make the Learning Sequence behave like the Exercise object.

10 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.