diff --git a/v1.19/_images/user/webhooks/authorization-header.png b/v1.19/_images/user/webhooks/authorization-header.png
new file mode 100644
index 00000000..06cd7055
Binary files /dev/null and b/v1.19/_images/user/webhooks/authorization-header.png differ
diff --git a/v1.19/user/webhooks.md b/v1.19/user/webhooks.md
index 280ed785..18de36e2 100644
--- a/v1.19/user/webhooks.md
+++ b/v1.19/user/webhooks.md
@@ -182,4 +182,8 @@ There is a Test Delivery button in the webhook settings that allows to test the
 
 ### Authorization header
 
-Forgejo hooks can be configured to send an [authorization header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization) to the webhook target.
+Forgejo webhooks can be configured to send an [authorization header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization) to the target.
+
+![screenshot of the webhook definition webpage](../../../../images/v1.19/user/webhooks/authorization-header.png)
+
+The authentication string is stored encrypted in the database.