diff --git a/docs/my-website/img/release_notes/guardrail_fallbacks.png b/docs/my-website/img/release_notes/guardrail_fallbacks.png
new file mode 100644
index 0000000000..306e5b62bb
Binary files /dev/null and b/docs/my-website/img/release_notes/guardrail_fallbacks.png differ
diff --git a/docs/my-website/release_notes/v1.83.3/index.md b/docs/my-website/release_notes/v1.83.3/index.md
index 6a7f2a5fbf..fa4115b533 100644
--- a/docs/my-website/release_notes/v1.83.3/index.md
+++ b/docs/my-website/release_notes/v1.83.3/index.md
@@ -71,8 +71,12 @@ The Skills Marketplace gives teams a self-hosted catalog for discovering, instal
 
 ### Guardrail Fallbacks
 
+![Guardrail Fallbacks](../../img/release_notes/guardrail_fallbacks.png)
+
 Guardrail pipelines now support an optional `on_error` behavior. When a guardrail check fails or errors out, you can configure the pipeline to fall back gracefully — logging the failure and continuing the request — instead of returning a hard 500 to the caller. This is especially useful for non-critical guardrails where availability matters more than enforcement.
 
+[Get Started](../../docs/proxy/guardrails/policy_flow_builder)
+
 ### Team Bring Your Own Guardrails
 
 Teams can now attach guardrails directly from the team management UI. Admins configure available guardrails at the project or proxy level, and individual teams select which ones apply to their traffic — no config file changes or proxy restarts needed. This also ships with project-level guardrail support in the project create/edit flows.