diff --git a/src/content/docs/cloudflare-one/email-security/detection-settings/allow-policies.mdx b/src/content/docs/cloudflare-one/email-security/detection-settings/allow-policies.mdx
index 1fa60e7f27d3a5b..e183ed566260369 100644
--- a/src/content/docs/cloudflare-one/email-security/detection-settings/allow-policies.mdx
+++ b/src/content/docs/cloudflare-one/email-security/detection-settings/allow-policies.mdx
@@ -5,6 +5,8 @@ sidebar:
   order: 1
 ---
 
+import { Example, Details } from "~/components"
+
 Email Security allows you to configure allow policies. An allow policy exempts messages that match certain patterns from normal detection scanning.
 
 To configure allow policies:
@@ -30,6 +32,55 @@ To configure allow policies:
    - **Uploading an allow policy**: Upload a file no larger than 150 KB. The file can only contain `Pattern`, `Pattern Type`, `Verify Email`, `Trusted Sender`, `Exempt Recipient`, `Acceptable Sender`, `Notes` fields. The first row must be a header row. Refer to [CSV uploads](/cloudflare-one/email-security/detection-settings/allow-policies/#csv-uploads) for an example file.
 6. Select **Save**.
 
+<Details header="Allow policy configuration use cases">
+    
+The following use cases present some use cases that will show you how to properly configure allow policies.
+
+### Use case 1
+
+<Example title = "Company receives emails from third party providers not used internally. These emails are sent from the service provider, but Email Security gives these emails an incorrect disposition.">
+    This use case can affect companies such as Shopify, PayPal, and Docusign.
+
+    To solve this:
+
+    1. Submit a [team submission](/cloudflare-one/email-security/email-monitoring/search-email/#team-submissions).
+    2. Inform your Cloudflare account about the escalation.
+    3. Avoid setting up allow policies, or blocked senders. In this use case, configuring allow policies will create a security gap. Setting up blocked senders will block legitimate emails from providers such as Shopify, PayPal, and Docusign.
+</Example>
+
+### Use case 2
+
+<Example title = "Company receives emails via third party providers that are used internally. These emails are sent from the custom domain company, but Email Security marks these emails as bulk, spam, or spoof.">
+
+  This use case can cause your inbox to receive too many unwanted emails. This use case can affect companies such as Salesforce, Atlassian, and Figma.
+
+  To solve this, when you add an allow policy in the Zero Trust dashboard, ensure that:
+  
+  1. You choose **Accept sender**.
+  2. Verify that **Sender verification (recommended)** is turned on.
+  
+</Example>
+
+
+### Use case 3
+
+<Example title = "Company receives emails via third party providers that are used internally. These emails are sent from the custom company domain, but Email Security marks these emails as bulk, spam, or spoof. The custom email domain does not support DMARC, SPF, DKIM, and would fail Sender Verification">
+
+  This use case can affect companies such as Salesforce, Atlassian, and Figma.
+
+  To solve this, when you add an allow policy in the Zero Trust dashboard, ensure that:
+
+  1. You choose **Accept sender** based on the static IP you own.
+  2. Ensure that **Sender verification (recommended)** is turned off.
+
+  :::caution
+  Do not use email addresses or email domains for this case as they can be easily spoofed without **Sender Verification (Recommended)** enabled.
+  :::
+ 
+</Example>
+
+</Details>
+
 ### CSV uploads
 
 You can upload a file no larger than 150 KB. The file can only contain `Pattern`, `Pattern Type`, `Verify Email`, `Trusted Sender`, `Exempt Recipient`, `Acceptable Sender`, `Notes`. The first row must be a header row.