From 33929483eea2c08f740161f185626c7f948d56fc Mon Sep 17 00:00:00 2001
From: Rafael Matsumoto <110425783+rafaelmatsumotomb@users.noreply.github.com>
Date: Thu, 5 Feb 2026 14:57:36 -0300
Subject: [PATCH] TASK-188262: Clarify subaccount suppression list isolation

Add documentation explaining that no inheritance exists between primary
account and subaccount suppression lists when sending with a subaccount key.
---
 content/docs/user-guide/using-suppression-lists.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/docs/user-guide/using-suppression-lists.md b/content/docs/user-guide/using-suppression-lists.md
index 145461ba1..ab040b3ec 100644
--- a/content/docs/user-guide/using-suppression-lists.md
+++ b/content/docs/user-guide/using-suppression-lists.md
@@ -10,7 +10,7 @@ SparkPost supports two types of suppression lists: one (available via the [Suppr
 
 When a message is injected either using SMTP or HTTP, SparkPost will check the email address against the account-specific and global suppression lists. If an email address for a recipient matches an address on the list, that message will be rejected for delivery by SparkPost automatically.
 
-**Note: each subaccount has its own separate suppression list which is separate from the primary account suppression list.**
+**Note:** Each subaccount has its own separate suppression list, which is separate from the primary account suppression list as explained in the [summary of subaccount features](/docs/user-guide/subaccounts#summary-of-subaccount-features). No inheritance behavior exists between the primary account and its subaccounts when sending with a subaccount key.
 
 ## How are [recipients](https://www.sparkpost.com/api#/reference/recipient-lists "Recipient List API") added to [suppression lists](https://www.sparkpost.com/api#/reference/suppression-list "Suppression List API")?