diff --git a/docs/my-website/release_notes/v1.81.14.md b/docs/my-website/release_notes/v1.81.14.md
index 73a9b5e28f1..7b9e64b6085 100644
--- a/docs/my-website/release_notes/v1.81.14.md
+++ b/docs/my-website/release_notes/v1.81.14.md
@@ -72,6 +72,9 @@ These guardrails are built for production and on our benchmarks had a 100% Recal
 
 Previously, the `store_model_in_db` setting could only be configured in `proxy_config.yaml` under `general_settings`, requiring a proxy restart to take effect. Now you can enable or disable this setting directly from the Admin UI without any restarts. This is especially useful for cloud deployments where you don't have direct access to config files or want to avoid downtime. Enable `store_model_in_db` to move model definitions from your YAML into the database—reducing config complexity, improving scalability, and enabling dynamic model management across multiple proxy instances.
 
+![Store model in DB Setting](../img/ui_store_model_in_db.png)
+
+
 #### Eval results
 
 We benchmarked our new built-in guardrails against labeled datasets before shipping. You can see the results for Denied Financial Advice (207 cases) and Denied Insults (299 cases):