From d626dfaacdad2d474548ff32da86c9b56b70f1ce Mon Sep 17 00:00:00 2001
From: Neil Kakkar <neilkakkar@gmail.com>
Date: Fri, 6 Aug 2021 12:30:24 +0100
Subject: [PATCH] Clarify how Filtering out internal users works

Got feedback that it was very confusing whether the filter is applied as is, or in negation. (as is makes sense for properties, but makes very little sense for cohorts, since internal users cohort size <<< external users cohort size)
---
 frontend/src/scenes/project/Settings/index.tsx | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/frontend/src/scenes/project/Settings/index.tsx b/frontend/src/scenes/project/Settings/index.tsx
index 8daed45f82d19..0b518b46b4a01 100644
--- a/frontend/src/scenes/project/Settings/index.tsx
+++ b/frontend/src/scenes/project/Settings/index.tsx
@@ -172,6 +172,10 @@ export function ProjectSettings(): JSX.Element {
                     company's team members, or <i>Host ∌ localhost</i> to exclude all events from local development
                     environments.
                 </p>
+                <p>
+                    <b>The filters you apply here are added as extra filters when the toggle is switched on.</b> So, if
+                    you apply a Cohort filter, it means toggling filtering on will match only this specific cohort.
+                </p>
                 <TestAccountFiltersConfig />
                 <Divider />
                 <h2 className="subtitle" id="urls">