feat: I need to be able to talk to my users. #3552

New Issue

GiteaMirror · 2025-11-11T15:33:49-06:00

GiteaMirror commented

2025-11-11 15:33:49 -06:00

Originally created by @abs-nikidinsey on GitHub (Feb 3, 2025).

Feature Request

Is your feature request related to a problem? Please describe.

We currently have around 100 pilot users accessing Open WebUI via Google SSO, and it's working fantastically for our school. However, I need a reliable way to communicate important information to users before rolling out the service further (another ~900 users). As the Admin, I must provide our users with clear details regarding GDPR compliance, privacy policies, and our school's AI usage policies. In the UK, we are required to be upfront about what data is stored, how it’s processed, and users’ rights regarding data deletion. Currently, there's no straightforward method to display these crucial notices directly within the app.

Describe the solution you'd like

I propose implementing a closable “growl” style notification that appears for all users across the application. The key requirements are:

Visibility and Interaction:
- The notification should be displayed to all users on any page and should be closable for the session.
- Since most users remain logged in, if the admin updates the notification, it should reset any “read/closed” state so that users see the updated message the next time they access the system.
Admin Configuration:
- The option should be accessible under Admin Settings > Settings > General.
- It should include a rich text editor that supports basic HTML formatting (e.g., bold, italics, anchors/links) so that policies and messages can be clearly formatted. Images are not required.
- A simple toggle should allow the admin to enable or disable the notification message.
Styling and Consistency:
- The notification should follow the current theme of the application in terms of style and colors.
- Given its intended usage (a few sentences at most), no extensive customization or character limit is required.
Technical Considerations:
- Our current installation method is via pip install, meaning we do not have easy access to modify the source JS files directly. An attempt to uncomment the “footer goes here” section in index.html resulted in the message flashing briefly on screen before disappearing.
- We need a solution that integrates with the application’s settings rather than requiring direct edits to compiled JS files.
- The notification is static and applies to all users. While it would be nice to have different messages for different user groups (e.g., staff vs. students), this is not a critical requirement for now.

Describe alternatives you've considered

I attempted to manually insert a footer by uncommenting the relevant section in index.html, but this approach was unsuccessful because the message only briefly appeared before disappearing. Additionally, a static footer or a message limited only to the login page would not satisfy our needs for ongoing compliance notifications throughout the user session.

Additional context

This feature is crucial for our continued use and expansion of Open WebUI. By implementing this admin-configurable notification system, we can effectively communicate important policy information—such as GDPR compliance, privacy practices, and AI policy usage—to all users. This is necessary for regulatory compliance and to maintain transparency with our users. Thank you for considering this request, and I appreciate all the work that has gone into making Open WebUI such a robust tool.

Originally created by @abs-nikidinsey on GitHub (Feb 3, 2025). # Feature Request **Is your feature request related to a problem? Please describe.** We currently have around 100 pilot users accessing Open WebUI via Google SSO, and it's working fantastically for our school. However, I need a reliable way to communicate important information to users before rolling out the service further (another ~900 users). As the Admin, I must provide our users with clear details regarding GDPR compliance, privacy policies, and our school's AI usage policies. In the UK, we are required to be upfront about what data is stored, how it’s processed, and users’ rights regarding data deletion. Currently, there's no straightforward method to display these crucial notices directly within the app. --- **Describe the solution you'd like** I propose implementing a closable “growl” style notification that appears for all users across the application. The key requirements are: - **Visibility and Interaction:** - The notification should be displayed to all users on any page and should be closable for the session. - Since most users remain logged in, if the admin updates the notification, it should reset any “read/closed” state so that users see the updated message the next time they access the system. - **Admin Configuration:** - The option should be accessible under **Admin Settings > Settings > General**. - It should include a rich text editor that supports basic HTML formatting (e.g., bold, italics, anchors/links) so that policies and messages can be clearly formatted. Images are not required. - A simple toggle should allow the admin to enable or disable the notification message. - **Styling and Consistency:** - The notification should follow the current theme of the application in terms of style and colors. - Given its intended usage (a few sentences at most), no extensive customization or character limit is required. - **Technical Considerations:** - Our current installation method is via `pip install`, meaning we do not have easy access to modify the source JS files directly. An attempt to uncomment the “footer goes here” section in `index.html` resulted in the message flashing briefly on screen before disappearing. - We need a solution that integrates with the application’s settings rather than requiring direct edits to compiled JS files. - The notification is static and applies to all users. While it would be nice to have different messages for different user groups (e.g., staff vs. students), this is not a critical requirement for now. --- **Describe alternatives you've considered** I attempted to manually insert a footer by uncommenting the relevant section in `index.html`, but this approach was unsuccessful because the message only briefly appeared before disappearing. Additionally, a static footer or a message limited only to the login page would not satisfy our needs for ongoing compliance notifications throughout the user session. --- **Additional context** This feature is crucial for our continued use and expansion of Open WebUI. By implementing this admin-configurable notification system, we can effectively communicate important policy information—such as GDPR compliance, privacy practices, and AI policy usage—to all users. This is necessary for regulatory compliance and to maintain transparency with our users. Thank you for considering this request, and I appreciate all the work that has gone into making Open WebUI such a robust tool.

GiteaMirror closed this issue

2025-11-11 15:33:49 -06:00

GiteaMirror commented

2025-11-11 15:33:49 -06:00

@taylorwilsdon commented on GitHub (Feb 3, 2025):

Already exists, you're looking for "Admin -> Settings -> Interface -> Banners" which will let you deploy a warning, info, error or success message that the user can close.

@taylorwilsdon commented on GitHub (Feb 3, 2025): Already exists, you're looking for "Admin -> Settings -> Interface -> Banners" which will let you deploy a warning, info, error or success message that the user can close.

GiteaMirror commented

2025-11-11 15:33:49 -06:00

@abs-nikidinsey commented on GitHub (Feb 3, 2025):

thank you @taylorwilsdon this will do! I can roll out to the whole cohort!

@abs-nikidinsey commented on GitHub (Feb 3, 2025): thank you @taylorwilsdon this will do! I can roll out to the whole cohort!

GiteaMirror referenced this issue

2026-04-19 20:05:01 -05:00

[GH-ISSUE #3552] Google OAuth authentication fails #13305

GiteaMirror referenced this issue

2026-04-25 03:22:46 -05:00

[GH-ISSUE #3552] Google OAuth authentication fails #28833

GiteaMirror referenced this issue