-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Self-Hosted] Proactive Admin notifications #9974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I like this. I guess we have to think about how we configure the broadcast medium. In ascending order of difficulty, I'd suggest something like:
|
Thanks for opening this, @lucasvaltl! This cought my attention! Usually such notifications are Using the new alert component sounds ideal for such in-product notications. For example, this is how we could warn users that prebuilds have been paused for inactive projects (see #9232). Given the upcoming navigation changes on the dashboard in #8385, a global alert component below the top navigations sounds ideal to host such notiications. For example, here's a quick design draft how this could look like with a non-dismissible global alert that persists across all pages in the dashboard for admins. @mrsimonemms
|
AppNotifications might be useful here. |
@lucasvaltl We further built out the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is your feature request related to a problem? Please describe
Currently, an admin of a self-hosted installation can only see the state of their installation regarding license if they proactively look into the license tab of the admin age themselves, or the KOTS Installation UI. This means that they might only get notified of an issue (e.g. out of seats) when it is too late, potentially causing inefficiencies with onboarding new users / employees.
Describe the behaviour you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: