diff --git a/plugin-designs/country-map/country-map.vue b/plugin-designs/country-map/country-map.vue
index fe1ebf3c1..52ffbc794 100644
--- a/plugin-designs/country-map/country-map.vue
+++ b/plugin-designs/country-map/country-map.vue
@@ -31,6 +31,7 @@ import { computed, inject, ref, onMounted, watch } from 'vue'
 import RegionCountryMap from '@map/components/maps/RegionCountryMap.vue'
 import { toNumber, PEOPLE_GROUP_LIST_FIELDS } from '@map/utils/countries-meta.js'
 import { peopleGroupPoints, PEOPLE_GROUP_POINT_FIELDS } from '@map/utils/peopleGroupPoints.js'
+import { applyPeopleGroupList } from '@map/lists/peopleGroupList.js'
 import { useRegionsI18n } from '@map/i18n/useRegionsI18n.js'
 
 const props = defineProps({
@@ -99,7 +100,20 @@ async function loadPoints() {
     const response = await fetch(url)
     if (!response.ok) throw new Error(`HTTP ${response.status}`)
     const data = await response.json()
-    const all = peopleGroupPoints(Array.isArray(data.posts) ? data.posts : [], toNumber)
+    // ★ THE HOST'S LIST IS APPLIED TO THE RAW POSTS, BEFORE THEY BECOME POINTS. `list` is a
+    // profile-config prop every other consumer of this endpoint honours — DataSourceManager,
+    // useDashboardData, useCsvExport, peopleGroupRecords and the people-groups grid all call
+    // applyPeopleGroupList on the rows they fetched. This element did not, so a host that asked for
+    // one curated list got the WHOLE endpoint drawn on its country map and nothing said so: the pins
+    // looked like data rather than like the wrong list. Applying it here, on data.posts rather than
+    // on the mapped points, is what keeps this element and a dashboard showing the same country from
+    // disagreeing about which groups are in it — the same reason the country filter below is
+    // client-side.
+    // The default list returns the rows untouched and makes no fetch, so an unconfigured host pays
+    // nothing; a list whose membership cannot be loaded yields NO groups rather than the wrong ones,
+    // which is applyPeopleGroupList's own contract and the safer failure for a prayer surface.
+    const posts = await applyPeopleGroupList(Array.isArray(data.posts) ? data.posts : [], cfg.value)
+    const all = peopleGroupPoints(posts, toNumber)
     // Filter HERE rather than asking the API for one country: the endpoint returns the whole list
     // and every other consumer in this repo filters client-side, so a country page and a dashboard
     // showing the same country cannot disagree about which groups are in it.