This feature request aims to introduce granular control over chat lifetime and data purging parameters, both at the system-wide and user-specific levels. By providing configurable quotas, open chat limits, and chat lifetimes, we can minimize storage of unused data, optimize resource utilization, and improve overall system performance for use at scale.
Proposed Features
UI Fields and Database:
Add configurable fields to the user interface and database for:
Quota: Maximum allowed chat length (e.g., number of messages)
Open Chats: Maximum number of concurrently open chats per user
Chat Lifetime: Duration after which a chat is automatically deleted
Default Values:
Establish default values for automatic deletion:
Max Chat Length: Define a standard maximum chat length
Max Open Chats: Set a default limit for concurrent open chats
Chat Lifetime: Specify a default duration for chat expiration
default values editable by administrators
User-Specific Overrides:
Allow administrators to override default values for individual users, providing flexibility in managing specific user requirements or addressing resource constraints.
If multiple user roles are added in the future, one value can be selected per user role.
Originally created by @Zarkhator03 on GitHub (Jul 9, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/3728
## Description
This feature request aims to introduce granular control over chat lifetime and data purging parameters, both at the system-wide and user-specific levels. By providing configurable quotas, open chat limits, and chat lifetimes, we can minimize storage of unused data, optimize resource utilization, and improve overall system performance for use at scale.
## Proposed Features
- **UI Fields and Database:**
- Add configurable fields to the user interface and database for:
- **Quota:** Maximum allowed chat length (e.g., number of messages)
- **Open Chats:** Maximum number of concurrently open chats per user
- **Chat Lifetime:** Duration after which a chat is automatically deleted
- **Default Values:**
- Establish default values for automatic deletion:
- **Max Chat Length:** Define a standard maximum chat length
- **Max Open Chats:** Set a default limit for concurrent open chats
- **Chat Lifetime:** Specify a default duration for chat expiration
- default values editable by administrators
- **User-Specific Overrides:**
- Allow administrators to override default values for individual users, providing flexibility in managing specific user requirements or addressing resource constraints.
- If multiple user roles are added in the future, one value can be selected per user role.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Zarkhator03 on GitHub (Jul 9, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/3728
Description
This feature request aims to introduce granular control over chat lifetime and data purging parameters, both at the system-wide and user-specific levels. By providing configurable quotas, open chat limits, and chat lifetimes, we can minimize storage of unused data, optimize resource utilization, and improve overall system performance for use at scale.
Proposed Features
UI Fields and Database:
Default Values:
User-Specific Overrides: