diff --git a/constructs/check-group-v2.mdx b/constructs/check-group-v2.mdx
index 43caa4d..13ec7f3 100644
--- a/constructs/check-group-v2.mdx
+++ b/constructs/check-group-v2.mdx
@@ -265,6 +265,15 @@ When referencing existing groups with `fromId()`, note:
 
 If you need these features, you can either import the group using the [Checkly import feature](/cli/checkly-import) (e.g. `npx checkly import check-group:123`) or define a new group directly in your project.
 
+## Shared Settings in Groups with Different Monitor Types
+
+With `CheckGroupV2` you can group uptime monitors (e.g. URL, TCP, DNS) and synthetic checks (e.g. API, Multistep, Playwright Check Suites). Depending on your plan type, some [group settings](/constructs/check-group-v2#configuration) (such as parallel runs or advanced retry strategies) may not be supported across both monitor types.
+
+To avoid conflicts, Checkly validates group settings against the lowest common denominator of supported features in the group.
+
+See [Mixing Checks and Monitors in a Group](/platform/groups/#mixing-checks-and-monitors-in-a-group) for details.
+
+
 ## Examples
 
 <Tabs>
diff --git a/platform/groups.mdx b/platform/groups.mdx
index 40812d4..51c621d 100644
--- a/platform/groups.mdx
+++ b/platform/groups.mdx
@@ -146,3 +146,17 @@ Groups can serve different organizational needs:
 - **Loose containers:** Provide structure without imposing shared settings
 - **Team boundaries:** Enable clear ownership and delegation of monitoring responsibilities
 - **Scaling mechanism:** Manage complexity through logical decomposition as your infrastructure grows
+
+
+## Mixing Checks and Monitors in a Group
+
+When you purchase a plan in Checkly, it includes access to specific monitoring features. As shown on our [pricing page](https://www.checklyhq.com/pricing), feature availability can differ between:
+
+* Uptime monitors (e.g. URL, TCP, DNS)
+* Synthetic checks (e.g. API, Multistep, Browser, Playwright Check Suites)
+
+This means monitors and checks on the same plan may not all have access to the same features. For example: A Browser check might support `parallel` scheduling, while a TCP monitor only allows for `round-robin` scheduling.
+
+Groups let you organize any type of checks/monitors together and define [shared settings](/platform/groups#configuration). If those shared settings aren't supported by all monitors in the group, Checkly will throw a validation error asking you to either adjust the configuration or remove the incompatible monitor.
+
+If you're unsure how to proceed, don't hesitate to reach out to our [support team](mailto:support@checklyhq.com), we're happy to help.
\ No newline at end of file