From ab735a3a2c8462dfdc77342a16e0cb2ac65efa35 Mon Sep 17 00:00:00 2001
From: paritosh-08 <85472423+paritosh-08@users.noreply.github.com>
Date: Mon, 3 Jul 2023 15:36:51 +0530
Subject: [PATCH] docs: add note for cloud users in auth-hook caching

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/9653
GitOrigin-RevId: ca61d3bdf42ac7b93521d320df787a1d47121d11
---
 docs/docs/auth/authentication/webhook.mdx | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/docs/auth/authentication/webhook.mdx b/docs/docs/auth/authentication/webhook.mdx
index 8e22cbbe997..521158e4007 100644
--- a/docs/docs/auth/authentication/webhook.mdx
+++ b/docs/docs/auth/authentication/webhook.mdx
@@ -249,9 +249,10 @@ Session variables from a webhook token can be cached to improve the performance
 :::info Note
 
 - This feature is available for version `v2.22.0` and higher.
-- Webhook auth caching requires a [redis instance configured](deployment/graphql-engine-flags/reference.mdx#redis-url)
-  with the GraphQL Engine. If the redis instance is not configured or inaccessible, then the request goes through by
-  skipping the cache.
+- Webhook auth caching is available on Hasura Cloud without any configuration.
+- For self-hosted EE, it requires a [Redis instance
+  to be configured](deployment/graphql-engine-flags/reference.mdx#redis-url). If the Redis instance is not configured or
+  inaccessible, then the request will skip the cache.
 
 :::