From 3070ba74aeefd28f082859bc68f53896c8d721db Mon Sep 17 00:00:00 2001
From: 0xsysr3ll <0xsysr3ll@pm.me>
Date: Mon, 15 Dec 2025 19:04:03 +0100
Subject: [PATCH] docs(webhook): clarify conflict between Authorization header
 methods

Signed-off-by: 0xsysr3ll <0xsysr3ll@pm.me>
---
 docs/using-seerr/notifications/webhook.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/using-seerr/notifications/webhook.md b/docs/using-seerr/notifications/webhook.md
index 34bd393ee..a63508b61 100644
--- a/docs/using-seerr/notifications/webhook.md
+++ b/docs/using-seerr/notifications/webhook.md
@@ -29,8 +29,8 @@ You can add additional custom HTTP headers to be sent with each webhook request.
 - Click "Add Header" to add a new header
 - Enter the header name and value
 
-:::info
-If you set an `Authorization` header here, it will only be used if the Authorization Header field above is empty (the Authorization Header field takes precedence)
+:::warning
+You cannot configure both the **Authorization Header** field and a custom `Authorization` header in Custom Headers at the same time. You must choose one method.
 :::
 
 ### JSON Payload