diff --git a/src/content/docs/agent-platform/inference/model-choice.mdx b/src/content/docs/agent-platform/inference/model-choice.mdx
index a44f2f33..3c0651e9 100644
--- a/src/content/docs/agent-platform/inference/model-choice.mdx
+++ b/src/content/docs/agent-platform/inference/model-choice.mdx
@@ -57,6 +57,9 @@ All Auto models perform well across all agent workflows and are ideal if you pre
 
 | Model | `model_id` | Variant |
 | --- | --- | --- |
+| Claude Fable 5 | `claude-5-fable-xhigh` | Default effort |
+| Claude Fable 5 | `claude-5-fable-high` | High effort |
+| Claude Fable 5 | `claude-5-fable-max` | Max effort |
 | Claude Opus 4.7 | `claude-4-7-opus-xhigh` | Default effort |
 | Claude Opus 4.7 | `claude-4-7-opus-high` | High effort |
 | Claude Opus 4.7 | `claude-4-7-opus-max` | Max effort |
@@ -70,6 +73,10 @@ All Auto models perform well across all agent workflows and are ideal if you pre
 | Claude Sonnet 4.5 | `claude-4-5-sonnet-thinking` | Thinking on |
 | Claude Haiku 4.5 | `claude-4-5-haiku` | — |
 
+:::caution
+Anthropic requires data retention for Claude Fable 5 for safety, abuse monitoring, and compliance reasons, so it is **not available under Zero Data Retention (ZDR)**. This requirement is specific to Claude Fable 5 and doesn't change the ZDR behavior of any other supported model. For Enterprise teams, the model is off by default and a workspace admin must enable it — see the [Admin Panel](/enterprise/team-management/admin-panel/#models-settings) and the [Security overview](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr).
+:::
+
 #### Google
 
 | Model | `model_id` |
@@ -133,3 +140,5 @@ Warp has executed **Zero Data Retention (ZDR)** agreements with these providers.
 * LLM providers commit to delete inputs and outputs after generating the relevant output, within a fixed time period.
 
 Warp enforces these commitments through both technical measures and contractual safeguards with the LLM providers.
+
+Zero data retention is available for supported models. Model availability may vary where providers require data retention for safety, abuse monitoring, or compliance reasons.
diff --git a/src/content/docs/enterprise/security-and-compliance/security-overview.mdx b/src/content/docs/enterprise/security-and-compliance/security-overview.mdx
index 2c8ba553..6eaf2652 100644
--- a/src/content/docs/enterprise/security-and-compliance/security-overview.mdx
+++ b/src/content/docs/enterprise/security-and-compliance/security-overview.mdx
@@ -34,6 +34,8 @@ How data collection works by plan:
 Some product features — including cloud conversations and Oz runs — require storing conversation data to function. This data is stored to power the product experience and is separate from analytics or telemetry data collection.
 :::
 
+Some models carry provider-specific data retention requirements and are therefore not covered by ZDR. For Enterprise teams, these models are **off by default**; a workspace admin must explicitly enable them in the [Admin Panel](/enterprise/team-management/admin-panel/#models-settings).
+
 Enterprise subscriptions also include:
 
 * **Team-level enforcement** - Admins configure data collection and telemetry policies for the entire organization through the Admin Panel
diff --git a/src/content/docs/enterprise/team-management/admin-panel.mdx b/src/content/docs/enterprise/team-management/admin-panel.mdx
index 6131200f..41c6dfe7 100644
--- a/src/content/docs/enterprise/team-management/admin-panel.mdx
+++ b/src/content/docs/enterprise/team-management/admin-panel.mdx
@@ -110,7 +110,7 @@ For complete plan details, see [Warp pricing](https://www.warp.dev/pricing) or [
 
 ## Admin Panel sections
 
-The Admin Panel is organized into six main areas:
+The Admin Panel is organized into seven main areas:
 
 ### AI settings
 
@@ -211,6 +211,14 @@ When enabled, agents understand your code patterns, architecture, and convention
 * Up to 200,000 files per repository
 * Team-wide indexing with centralized configuration
 
+### Models settings
+
+Control which LLM models are available to your team and how inference is routed. From the **Models** page, admins can enable or disable individual models and configure [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) routing through AWS Bedrock.
+
+**Models with provider-specific data retention requirements**
+
+Some models require data retention from the model provider and are therefore not available under [Zero Data Retention (ZDR)](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr). For Enterprise teams, these models are **disabled by default**. A workspace admin must explicitly enable them before team members can use them.
+
 ### Billing settings
 
 Configure billing preferences and spending controls to manage costs at scale.
diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx
index 6b2a8f5f..6a1b7846 100644
--- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx
+++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx
@@ -242,6 +242,8 @@ Warp integrates with multiple LLM providers — including Anthropic, OpenAI, Goo
 
 Warp enforces these commitments through both technical measures and contractual safeguards with the LLM providers.
 
+Zero data retention is available for supported models. Model availability may vary where providers require data retention for safety, abuse monitoring, or compliance reasons.
+
 ### How can I enable Zero Data Retention in Warp?
 
 Zero Data Retention (ZDR) can be enabled in two ways: