The ability to create system notifications/PSAs in AEM Headless - Status changed to: Investigating

[#1]

Request for Feature Enhancement (RFE) Summary:	Implement PSAs so that they can appear in all of the AEM UIs
Use-case:	The content operations team is looking to create a PSA or Alert bar/popup that would appear for all/some users on the platform when they log in.
Current/Experienced Behavior:	Adobe proposed this solution: https://adobe-consulting-services.github.io/acs-aem-commons/features/system-notifications/index.html Results research: I have researched and tried out the ACS Commons System Notifications in the past already. Those only work in the "old" AEM UI, not in the "new" CF Admin/Editor or Universal Editor. So any author directly going into those UIs would never see the notifications. And even authors accessing the old UI might be confused since it disappears on the new UIs. They might think only the old UI is affected by whatever the notification says.
Improved/Expected Behavior:	1- it would stay up as long as we need it (if we posted a message about an outage or major incident, we'd want to disable it once the situation was resolved) 2- it would be an informative message related to an outage or major incident - example: We’re currently aware of an issue affecting all pre-owned inventory, including Certified Pre-Owned (CPO) pages, on oADD live sites where inventory is not rendering as expected. Our team is actively engaged with our development team to work towards a solution. 3- Permissions: Only admins can create (we need to centralize it and restrict it to one decision making group). 4-This PSA should NOT require developer involvement to create  5- Ability to show it to only specific user groups. For example, we want to show a specific message to French content authors in Canada
Environment Details (AEM version/service pack, any other specifics if applicable):
Customer-name/Organization name:	Audi
Screenshot (if applicable):
Code package (if applicable):

[#2]

@AnasEl5 Thanks for proposing this idea. This has been reported to the engineering under the internal reference SITES-35880. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.