Feature Wiki

Information about planned and released features

Tabs

Administrative Push Notification

1 Initial Problem

In situations such as scheduled maintenance or newly regarded bugs, there is often a lack of a fast and reliable communication channel between administrators and users. This gap can result in user frustration, due to a lack of information. Moreover, administrators typically have no straightforward way to test the push notification interface or send controlled test messages in advance and Testing Scenarios.

2 Conceptual Summary

Implementing push notification capabilities for administrators ensures that important messages—like (un)planned maintenance alerts and other urgent notifications — are delivered instantly and reliably. This direct communication channel minimizes confusion caused by a lack of information and therefore enhances user experience. Furthermore, adminsitrators have a opportunity to test the Push-Notication configuration.

If an administrative Push-Notification is send, all Users (when have activated the Push-Notifications in personell settings and Browser/OS) will receive this message. This option is intended to complement the existing administrative notification options, not replace or duplicate them. Therefore, push notifications should not be sent automatically when the existing administrative notification options are used.

The User always will have the possibilty to deselect these kind of notification.

3 User Interface Modifications

3.1 List of Affected Views

  • Personal Settings / Push-Notification
  • Administration / Communication / Administrative Notification

3.2 User Interface Details

The Administrative Notification will be listed within the Push-Notification Provider Form

A Button will be provided at the as second Option under Administrative Notifications

A Input Form shall be provided.

Optional:

A Selection of Gobal Roles can be provided to send Notifications to selected (Multiselect) Roles.

A Modal shall be presented to confirm Sending the Push-Notifications

3.3 New User Interface Concepts

None

3.4 Accessibility Implications

Due to the Usage of KS-elements no a11y implications have to be considered. The accessibility of the Push Notification itself depends on the Browser and the OS used.

4 Additional Information

4.1 Involved Authorities

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:  Stake, Sebastian [sstake]

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: 8. Jul 2025, 13:29, Stake, Sebastian [sstake]