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 may lead to immediate closure of the PR.
Description: Provide a concise description of the changes made in this pull request.
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
This pull request clarifies the distinct purposes of the two webhook URL fields in the user and admin settings. Previously, their functions were not clearly defined in the UI, leading to potential confusion. By adding descriptive helper text, we make it explicit what event triggers each webhook, improving the overall user experience for both administrators and regular users.
Added
Added descriptive text below the "Notification Webhook" input field in the user account settings to clarify its purpose.
Added descriptive text below the "Webhook URL" input field in the admin general settings to clarify its purpose.
Changed
Updated the user settings UI (Account.svelte) to provide a clear explanation for the notification webhook.
Updated the admin settings UI (General.svelte) to provide a clear explanation for the system-wide webhook.
Additional Information
The user-facing "Notification Webhook" is now described as triggering on completed chat responses when the user is inactive.
The admin-facing "Webhook URL" is now described as triggering on new user sign-up events.
This change helps prevent misconfiguration and ensures users understand what information they will receive from each webhook.
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.
🔄 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/18625
**Author:** [@silentoplayz](https://github.com/silentoplayz)
**Created:** 10/26/2025
**Status:** ❌ Closed
**Base:** `dev` ← **Head:** `clarify-webhook-settings`
---
### 📝 Commits (1)
- [`1b98f77`](https://github.com/open-webui/open-webui/commit/1b98f779ea582d6abe54a3f3a4dccb93b10b9933) feat: improve webhook descriptions
### 📊 Changes
**2 files changed** (+10 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `src/lib/components/admin/Settings/General.svelte` (+5 -0)
📝 `src/lib/components/chat/Settings/Account.svelte` (+5 -0)
</details>
### 📄 Description
# Pull Request Checklist
**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 may lead to immediate closure of the PR.
- [X] **Description:** Provide a concise description of the changes made in this pull request.
- [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.
- [X] **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
- This pull request clarifies the distinct purposes of the two webhook URL fields in the user and admin settings. Previously, their functions were not clearly defined in the UI, leading to potential confusion. By adding descriptive helper text, we make it explicit what event triggers each webhook, improving the overall user experience for both administrators and regular users.
### Added
- Added descriptive text below the "Notification Webhook" input field in the user account settings to clarify its purpose.
- Added descriptive text below the "Webhook URL" input field in the admin general settings to clarify its purpose.
### Changed
- Updated the user settings UI (`Account.svelte`) to provide a clear explanation for the notification webhook.
- Updated the admin settings UI (`General.svelte`) to provide a clear explanation for the system-wide webhook.
---
### Additional Information
- The user-facing "Notification Webhook" is now described as triggering on completed chat responses when the user is inactive.
- The admin-facing "Webhook URL" is now described as triggering on new user sign-up events.
- This change helps prevent misconfiguration and ensures users understand what information they will receive from each webhook.
- Related update to the docs repo - https://github.com/open-webui/docs/pull/780
### Screenshots or Videos
<img width="1146" height="676" alt="image" src="https://github.com/user-attachments/assets/4dbed4e2-1bdd-4c16-94e5-ee383af13c24" />
<img width="2104" height="110" alt="image" src="https://github.com/user-attachments/assets/6120b5f8-afc5-488c-963c-4c33c75f5fbe" />
### 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.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/18625
Author: @silentoplayz
Created: 10/26/2025
Status: ❌ Closed
Base:
dev← Head:clarify-webhook-settings📝 Commits (1)
1b98f77feat: improve webhook descriptions📊 Changes
2 files changed (+10 additions, -0 deletions)
View changed files
📝
src/lib/components/admin/Settings/General.svelte(+5 -0)📝
src/lib/components/chat/Settings/Account.svelte(+5 -0)📄 Description
Pull Request Checklist
Before submitting, make sure you've checked the following:
devbranch. Not targeting thedevbranch may lead to immediate closure of the PR.Changelog Entry
Description
Added
Changed
Account.svelte) to provide a clear explanation for the notification webhook.General.svelte) to provide a clear explanation for the system-wide webhook.Additional Information
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.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.