Merge pull request #314 from Portkey-AI/cache-ttl

cache TTL page update

Author: vrushankportkey

product/ai-gateway/cache-simple-and-semantic.mdx

@@ -95,6 +95,32 @@ In this example, your cache will automatically expire after 60 seconds. Cache ag
 </Info>
 ---
 
+
+## Organization-Level Cache TTL Settings
+
+Organization administrators can now define the default cache TTL (Time to Live) for all API keys and workspaces within the organization. This provides centralized control over cache expiration to align with data retention policies.
+
+**How to Configure Organization Cache TTL**
+1. Navigate to Admin Settings
+2. Select Organization Properties
+3. Scroll to Cache Settings
+4. Enter your desired default cache TTL value (in seconds)
+5. Click Save
+
+### How Organization-Level Cache TTL Works
+
+1. **Default Value**: The value set at the organization level serves as both the maximum and default TTL value.
+2. **Precedence Rules**:
+   - If no `max_age` is specified in the request, the organization-level default value is used.
+   - If the `max_age` value in a request is greater than the organization-level default, the organization-level value takes precedence.
+   - If the `max_age` in a request is less than the organization-level default, the lower request value is honored.
+3. The max value of Organisation Level Cache TTL is 25923000 seconds.
+<Info>
+This feature helps organizations implement consistent cache retention policies while still allowing individual requests to use shorter TTL values when needed.
+</Info>
+
+
+
 ## Force Refresh Cache
 
 Ensure that a new response is fetched and stored in the cache even when there is an existing cached response for your request. Cache force refresh can only be done **at the time of making a request**, and it is **not a part of your Config**.