Feature Wiki
Tabs
Membership History
Page Overview
[Hide]- Functionaility formerly entailed in this request was separated to following separate request: Membership History in Staff
1 Initial Problem
Oftentimes HR requires ILIAS to offer a more comprehensive set of 'Member Statuses' that ILIAS offers. This set typically includes 'Cancelled' and 'Requested'.
They deal with disgruntled participants and trainers claiming to have been treated somewhat unfairly with regard to some course admission. These disputs are tiresome and could be resolved by information. It is important to them to understand which Members unsubscribed themselves or were unsubscribed by a webservice or a Course Administrator and when. The same is true for the question when Membership was requested and who granted it when.
We consider this a valid need, however 'Cancelled' and 'Requested' are no statuses but events. This warrants a log or history.
This informational need should be served with privacy in mind.
2 Conceptual Summary
Global Activation of Log
The log should be globally activated in Administration > Repsoitory and Objects > Course. It is similar to the RBAC log. This means that a duration or 'shelf life' of the log entries can be put in.
The following Event Data is to be stored in Membership Service.
- Object Type
- Object ID
- Object Title (in case object was deleted)
- Reference ID
- User ID of Agent / User who did it
- User ID of Member / Prospective Member User done to
- ILIAS component (e.g. Service/Membership)
- Event (see below)
- Datetime of Event
Event | Description |
|---|---|
User Requested Membership | User has applied to become a member, awaits approval |
User Approves Membership Request | Agent has approved Membership of User |
User Joined | User has become a member of the course |
User Unsubscribed | User unsubsribed from course |
User Added Manually | User was added to course manually by agent with 'Manage Members' permission |
User Auto-Filled from Waiting List | User was added to the course from the waiting list automatically |
User Added from Waiting List Manually | User was added to the course from the waiting list manually by agent with 'Manage Members' permission |
3 User Interface Modifications
3.1 List of Affected Views
- Administration > Repository and Objects > Course
- Course >
3.2 User Interface Details
New Sub-tab in Administration > Repository and Objects > Course
Log in Course3.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
- We need to be able to export the logs since they comprise personal data. Export should be offered in the "Export/Import"-tab of the Personal Profile. Data fields comprising personal data of others need to be set to [anonymous].
- If a user is deleted the Firstname, Lastname and Login will be set to anonymous in all logs.
- Logging only starts once the setting is set and stops, once the setting is deselected. Start and end of logging shall be displayed in al enrolment logs.
6 Security Implications
No foreseen security implications
7 Contact
- Author of the Request: Tödt, Alexandra [atoedt]
- Maintainer: Meyer, Stefan [smeyer]
- Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}
8 Funding
- …
9 Discussion
- You may want to also log de/activation of the log itself as a global event. Otherwise the log will be disputable. I.e. anyone could claim that the log might have been disabled for a short time, or something.
- Please include also the following actions to the enrolment log:
- User joined
- Added manually
- Add from waitinglist manually
- Autofill from waitinglist (by ILIAS)
- Additional filter for all supported actions (multi-select)
- Start and end of logging shall be displayed in all enrolment logs.
Statement of 29/04/2026:
This feature was discussed in the Privacy Clinic. We believe the need for collecting and storing the data is well-founded; platforms can use this feature based on legitimate interest or legal grounds.The data collection appears to be minimal, and the feature takes retention and deletion periods into account.
10 Implementation
{The maintainer has to give a description of the final implementation and add screenshots if possible.}
Test Cases
- {Test case number linked to Testrail} : {test case title}
Approval
Approved at {date} by {user}.
Last edited: 29. Apr 2026, 13:25, Seidel, Elyesa [seidel]