Feature Wiki
Tabs
Permanent-Link for Contacts, News, Badges, Mail
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 3.1 List of Affected Views
- 3.2 User Interface Details
- 3.2.1 Contacts ›› My Contacts
- 3.2.2 Contacts ›› Mailing Lists
- 3.2.3 Contacts ›› My Courses
- 3.2.4 Contacts ›› My Groups
- 3.2.5 News
- 3.2.6 Badges
- 3.2.7 Mail ›› Folder
- 3.2.8 Mail ›› Compose
- 3.2.9 Mail ›› Read a Mail & ›› Reply to a Mail
- 3.3 New User Interface Concepts
- 3.4 Accessibility Implications
- 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
1 Initial Problem
Currently, there is no permanent or static link that allows users or third-party systems to directly reference the following pages/screens (marked in strong):
- Contacts
- My Contacts
- My Courses
- My Groups
- Mailing Lists
- News
- Badges
- Mail
- Folder (shows Inbox)
- Compose
- Read a Mail
- Reply to a Mail
This limitation prevents users from:
- bookmarking those screens.
- receiving direct links to those screens in e-mails or notifications (e.g by plugins, or later, the core).
- integrating the link into external systems (e.g., intranets or portals).
Without a stable URL endpoint, there is no reliable way for users to return to those screens unless they navigate through the interface manually. This affects both usability and the integration potential of ILIAS in external workflows.
2 Conceptual Summary
To address this issue, the feature proposes the introduction of a permanent link to the listed screens. This link would be exposed in the ILIAS footer, making it easily accessible from anywhere in the system.
The link will:
- Always point to the screens of the currently logged-in user.
- Be usable in external systems, bookmarks, or e-mails as a reliable navigation target.
- Redirect unauthenticated users to the login page first, and upon successful authentication, return them directly to the screen.
This approach ensures a robust, user-friendly mechanism for referencing and sharing information in a consistent way across user sessions and system boundaries.
3 User Interface Modifications
3.1 List of Affected Views
- Contacts ›› My Contacts - go/contacts/overview
- Contacts ›› My Courses - go/contacts/mygroups
- Contacts ›› My Groups - go/contacts/mycourses
- Contacts ›› Mailing Lists - go/contacts/mailinglists
- News - go/news/overview
- Badges - go/badges/overview
- Mail ›› Folder - go/mail/inbox
- Mail ›› Compose - go/mail/compose
- Mail ›› Read a Mail - go/mail/4711/read
- Mail ›› Reply to a Mail - go/mail/4711/reply
3.2 User Interface Details
3.2.1 Contacts ›› My Contacts
Before
After
3.2.2 Contacts ›› Mailing Lists
This tab is only shown, if the user has at least one contact. If the Permanent-Link has been accessed without having any contacts, the user is redirected to the tab "My Contacts" and a Failure Messagebox is shown.
Before
After
3.2.3 Contacts ›› My Courses
Before
After
3.2.4 Contacts ›› My Groups
Before
After
3.2.5 News
Before
After
3.2.6 Badges
Before
After
3.2.7 Mail ›› Folder
Before
After
3.2.8 Mail ›› Compose
Before
After
3.2.9 Mail ›› Read a Mail & ›› Reply to a Mail
For reading and replying a mail and a mail a Permanent-Link is technically provided. This link is not shown at the User-Interface.
This is to be used at the cronjob "New Mail Notifications" in the future.
3.3 New User Interface Concepts
No new User Interface Concepts needed
3.4 Accessibility Implications
No Accessbility Implications
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Jansen, Michael [mjansen], Samoila, Oliver [oliver.samoila]
- Authority to Sign off Code Changes: Jansen, Michael [mjansen], Joußen, Thomas [tjoussen]
4.2 Technical Aspects
The `StaticURL` component will be used for link handling.
4.3 Privacy
No new Personal Data used or stored
4.4 Security
No changes relevant to security aspects. Adaptation of existing patterns.
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Samoila, Oliver [oliver.samoila]
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
Kunkel, Matthias [mkunkel], 24 SEP 2025: Have you already a plan how the permalinks look like?
Lowe, Simon [simon.lowe], 25 SEP 2025: Thank's for the question Matthias - I have added them at the chapter 3.1.
JourFixe, ILIAS [jourfixe], 29 SEP 2025: We highly appreciate this suggestion and accept the feature for trunk.
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: 1. Oct 2025, 10:33, Wolf, Fabian [fwolf]