[PR #20462] [MERGED] feat: Memories Feature Toggle & Granular Permissions #112945

New Issue

GiteaMirror · 2026-05-18T13:11:00-05:00

GiteaMirror commented

2026-05-18 13:11:00 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/20462
Author: @silentoplayz
Created: 1/7/2026
Status: ✅ Merged
Merged: 1/7/2026
Merged by: @tjbck

Base: dev ← Head: feat/memories-permission

📝 Commits (1)

363808f feat: implement global memories toggle and permissions

📊 Changes

10 files changed (+152 additions, -5 deletions)

View changed files

📝 backend/open_webui/config.py (+11 -0)
📝 backend/open_webui/main.py (+3 -0)
📝 backend/open_webui/routers/auths.py (+4 -0)
📝 backend/open_webui/routers/memories.py (+99 -4)
📝 backend/open_webui/routers/users.py (+1 -0)
📝 src/lib/components/admin/Settings/General.svelte (+8 -0)
📝 src/lib/components/admin/Users/Groups/Permissions.svelte (+16 -0)
📝 src/lib/components/chat/SettingsModal.svelte (+7 -0)
📝 src/lib/constants/permissions.ts (+2 -1)
📝 src/lib/stores/index.ts (+1 -0)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

Before submitting, make sure you've checked the following:

Target branch: Verify that the pull request targets the dev branch. Not targeting the dev branch will lead to immediate closure of the PR.
Description: Provide a concise description of the changes made in this pull request down below.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: If necessary, update relevant documentation Open WebUI Docs like environment variables, the tutorials, or other documentation sources.
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it in the PR description.
Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Implemented a robust feature toggle system for "Memories". This PR introduces a global On/Off switch for the Memories feature in the Admin Settings, as well as granular permission controls for individual user roles. It ensures that when the feature is disabled globally, all related UI elements (including the Personalization tab) are hidden for all users, including admins.

Added

Global Config: Added ENABLE_MEMORIES configuration and a corresponding UI toggle in Admin > Settings > General > Features.
Permissions: Added "Memories" to the Features Permissions list in Admin > Users > Permissions.
API: Exposed enable_memories in the /api/config endpoint to allow the frontend to react to the global state.

Changed

UI Logic: Updated SettingsModal.svelte to conditionally hide the "Personalization" (Memories) tab based on the global enable_memories config.
Backend Logic: Refactored memories.py to enforce both the global ENABLE_MEMORIES check and the granular features.memories permission on all endpoints.

Security

Added server-side validation to block access to Memories API endpoints (/api/v1/memories/*) if the feature is disabled globally or if the user lacks the specific permission.

Additional Information

This change ensures that "Memories" follows the same configuration pattern as other major features like Image Generation and Web Search, providing consistent administrative control.
This change addresses the community request to allow administrators to fully disable the Memories feature, as discussed in Discussion #17018.

Would love to see this feature. In my case not to enable it globally but to disable it so that users cannot use the feature at all anymore.

This PR implements precisely that capability, along with granular control for those who want to enable it selectively.

Screenshots or Videos

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/20462 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 1/7/2026 **Status:** ✅ Merged **Merged:** 1/7/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `feat/memories-permission` --- ### 📝 Commits (1) - [`363808f`](https://github.com/open-webui/open-webui/commit/363808f0b45ccd9513b7fdf17ef9ce88bf418419) feat: implement global memories toggle and permissions ### 📊 Changes **10 files changed** (+152 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/config.py` (+11 -0) 📝 `backend/open_webui/main.py` (+3 -0) 📝 `backend/open_webui/routers/auths.py` (+4 -0) 📝 `backend/open_webui/routers/memories.py` (+99 -4) 📝 `backend/open_webui/routers/users.py` (+1 -0) 📝 `src/lib/components/admin/Settings/General.svelte` (+8 -0) 📝 `src/lib/components/admin/Users/Groups/Permissions.svelte` (+16 -0) 📝 `src/lib/components/chat/SettingsModal.svelte` (+7 -0) 📝 `src/lib/constants/permissions.ts` (+2 -1) 📝 `src/lib/stores/index.ts` (+1 -0) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Verify that the pull request targets the `dev` branch. **Not targeting the `dev` branch will lead to immediate closure of the PR.** - [x] **Description:** Provide a concise description of the changes made in this pull request down below. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** If necessary, update relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs) like environment variables, the tutorials, or other documentation sources. - [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Take this as an opportunity to **make screenshots of the feature/fix and include it in the PR description**. - [x] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description Implemented a robust feature toggle system for "Memories". This PR introduces a global On/Off switch for the Memories feature in the Admin Settings, as well as granular permission controls for individual user roles. It ensures that when the feature is disabled globally, all related UI elements (including the Personalization tab) are hidden for all users, including admins. ### Added - **Global Config**: Added `ENABLE_MEMORIES` configuration and a corresponding UI toggle in **Admin > Settings > General > Features**. - **Permissions**: Added "Memories" to the Features Permissions list in **Admin > Users > Permissions**. - **API**: Exposed `enable_memories` in the `/api/config` endpoint to allow the frontend to react to the global state. ### Changed - **UI Logic**: Updated `SettingsModal.svelte` to conditionally hide the "Personalization" (Memories) tab based on the global `enable_memories` config. - **Backend Logic**: Refactored `memories.py` to enforce both the global `ENABLE_MEMORIES` check and the granular `features.memories` permission on all endpoints. ### Security - Added server-side validation to block access to Memories API endpoints (`/api/v1/memories/*`) if the feature is disabled globally or if the user lacks the specific permission. --- ### Additional Information - This change ensures that "Memories" follows the same configuration pattern as other major features like Image Generation and Web Search, providing consistent administrative control. - This change addresses the community request to allow administrators to fully disable the Memories feature, as discussed in [Discussion #17018](https://github.com/open-webui/open-webui/discussions/17018#discussioncomment-15435966). > Would love to see this feature. In my case not to enable it globally but to disable it so that users cannot use the feature at all anymore. This PR implements precisely that capability, along with granular control for those who want to enable it selectively. ### Screenshots or Videos <img width="2080" height="332" alt="image" src="https://github.com/user-attachments/assets/cfe0f575-f5fe-4474-8171-5a8de99f5758" /> <img width="908" height="571" alt="image" src="https://github.com/user-attachments/assets/e9c6d684-98ee-4143-a1fc-41cf6f45a22e" /> <img width="1354" height="761" alt="image" src="https://github.com/user-attachments/assets/8f1ada53-922a-49e6-8fe2-f114998b7707" /> ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-18 13:11:00 -05:00

GiteaMirror closed this issue

2026-05-18 13:11:02 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#112945