github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 07:43:10 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

feat: Feature Request: Option to Disable Administrator Access to User Chat Histories #4715

New Issue
Closed
opened 2025-11-11 16:01:18 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-11 16:01:18 -06:00
Owner
Copy Link

Originally created by @manwallet on GitHub (Apr 4, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Description

Currently, administrators can view all chat histories of registered users. This creates privacy concerns for users who want their conversations to remain confidential, even from the server administrator. As a server host who wants to provide OpenWebUI services to friends and other users, I need a way to ensure their privacy and build trust by technically restricting my own access to their conversations.

Proposed Solution

Implement a system setting that allows administrators to disable their ability to view users' chat histories. This could be:

  • A global toggle in admin settings that, when enabled, prevents administrators from accessing any user conversations
  • Potentially user-controlled privacy settings that let individuals choose whether their chats can be viewed by administrators
  • End-to-end encryption for chat sessions where the user holds the keys

Use Cases

  • Hosting a server for friends, family, or colleagues where privacy is a concern
  • Organizations that need to comply with privacy regulations
  • Educational environments where student privacy needs to be maintained

Benefits

  • Increased user trust and confidence in the platform
  • Better privacy protection for all users
  • Alignment with privacy-focused values and principles
  • Competitive advantage over platforms without such privacy controls

Additional Context

This feature is important for building trust when sharing an OpenWebUI server with other users. Many users are hesitant to use shared AI services if they believe their conversations could be viewed by administrators.

Thank you for considering this feature request.

Desired Solution you'd like

Desired Solution

I suggest implementing a simple and straightforward user authorization mechanism:

  1. User Authorization for Access:

    • By default, administrators cannot view any user's chat history
    • If an administrator needs to view a user's chat history (e.g., for troubleshooting), the system will send an authorization request to that user
    • Users can choose to approve or deny viewing requests
    • Users can set the time range for authorization (e.g., valid for 24 hours) and viewing scope (e.g., only specific conversations)
    • All authorization requests and access actions are logged in the system

  2. Interface Implementation:

    • Add a "Request to View Chat History" button in the admin panel
    • Users can manage authorization requests in their settings page after receiving notifications
    • The system displays which chat records are being viewed by administrators and when the authorization expires

This approach is both simple and effective in protecting user privacy while allowing administrators to provide support when necessary with explicit permission.

Alternatives Considered

No response

Additional Context

No response

Originally created by @manwallet on GitHub (Apr 4, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description ## Description Currently, administrators can view all chat histories of registered users. This creates privacy concerns for users who want their conversations to remain confidential, even from the server administrator. As a server host who wants to provide OpenWebUI services to friends and other users, I need a way to ensure their privacy and build trust by technically restricting my own access to their conversations. ## Proposed Solution Implement a system setting that allows administrators to disable their ability to view users' chat histories. This could be: - A global toggle in admin settings that, when enabled, prevents administrators from accessing any user conversations - Potentially user-controlled privacy settings that let individuals choose whether their chats can be viewed by administrators - End-to-end encryption for chat sessions where the user holds the keys ## Use Cases - Hosting a server for friends, family, or colleagues where privacy is a concern - Organizations that need to comply with privacy regulations - Educational environments where student privacy needs to be maintained ## Benefits - Increased user trust and confidence in the platform - Better privacy protection for all users - Alignment with privacy-focused values and principles - Competitive advantage over platforms without such privacy controls ## Additional Context This feature is important for building trust when sharing an OpenWebUI server with other users. Many users are hesitant to use shared AI services if they believe their conversations could be viewed by administrators. Thank you for considering this feature request. ### Desired Solution you'd like # Desired Solution I suggest implementing a simple and straightforward user authorization mechanism: 1. **User Authorization for Access**: - By default, administrators cannot view any user's chat history - If an administrator needs to view a user's chat history (e.g., for troubleshooting), the system will send an authorization request to that user - Users can choose to approve or deny viewing requests - Users can set the time range for authorization (e.g., valid for 24 hours) and viewing scope (e.g., only specific conversations) - All authorization requests and access actions are logged in the system 2. **Interface Implementation**: - Add a "Request to View Chat History" button in the admin panel - Users can manage authorization requests in their settings page after receiving notifications - The system displays which chat records are being viewed by administrators and when the authorization expires This approach is both simple and effective in protecting user privacy while allowing administrators to provide support when necessary with explicit permission. ### Alternatives Considered _No response_ ### Additional Context _No response_
GiteaMirror commented 2025-11-11 16:01:19 -06:00
Author
Owner
Copy Link

@gaby commented on GitHub (Apr 4, 2025):

@manwallet This already exists, see the docs:

https://docs.openwebui.com/getting-started/env-configuration#enable_admin_chat_access

ENABLE_ADMIN_CHAT_ACCESS=False
@gaby commented on GitHub (Apr 4, 2025): @manwallet This already exists, see the docs: https://docs.openwebui.com/getting-started/env-configuration#enable_admin_chat_access ```yaml ENABLE_ADMIN_CHAT_ACCESS=False ```
GiteaMirror commented 2025-11-11 16:01:19 -06:00
Author
Owner
Copy Link

@manwallet commented on GitHub (Apr 4, 2025):

@manwallet This already exists, see the docs:

https://docs.openwebui.com/getting-started/env-configuration#enable_admin_chat_access

ENABLE_ADMIN_CHAT_ACCESS=False

My bad
thank you very very much

@manwallet commented on GitHub (Apr 4, 2025): > [@manwallet](https://github.com/manwallet) This already exists, see the docs: > > https://docs.openwebui.com/getting-started/env-configuration#enable_admin_chat_access > > ENABLE_ADMIN_CHAT_ACCESS=False My bad thank you very very much
GiteaMirror commented 2025-11-11 16:01:20 -06:00
Author
Owner
Copy Link

@gaby commented on GitHub (Apr 4, 2025):

@manwallet No problem, please close the issue as completed

@gaby commented on GitHub (Apr 4, 2025): @manwallet No problem, please close the issue as completed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4715
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?