Feature Wiki
Tabs
Adding multiple users at once
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.
1 Initial Problem
There is no easy and fast way to add multiple members to a course/group. You can send a link for joining but usually not all recipients will join afterwards. This poses problems when communicating via "mail to members", because not everyone will get it. The same is true, when handling papers via the excercise: even when adding all course members to the excercise, you still need to check wether all participants are also members of the course.
The alternative is to add all members manually but this takes time, especially with higher participant numbers and multiple courses.
2 Conceptual Summary
Extending the present process of manualy adding users by being able to add several names and add them in the same role at the end, would reduce the amount of clicking needed.
It would also be helpful to be able to add users via excel/csv-list.
- either via First-/Lastnames. ILIAS would then need to suggest the correct users in cases of users having the same name or ILIAS not being able to find the name because of a typo or different spelling. This is probably difficult.
- by uploading a list with ILIAS usernames and coresponding roles.
3 User Interface Modifications
3.1 List of Affected Views
- … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }
3.2 User Interface Details
{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }
3.3 New User Interface Concepts
{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }
3.4 Accessibility Implications
{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: {Please add related profile link of this person}
- Authority to Sign off Code Changes: {Please add related profile link of this person}
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }
4.3 Privacy
{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }
4.4 Security
{ 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. }
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Heidmann, Jessica [jheidmann]
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
5 Discussion
6 Implementation
Feature has been implemented by {Please add related profile link of this person}
6.1 Description and Screenshots
{ Description of the final implementation and screenshots if possible. }
6.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
6.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
6.4 Approval
Approved at {date} by {user}.
Last edited: 23. Jul 2025, 16:44, Heidmann, Jessica [jheidmann]