[hturnbull93]

Screenshots: https://fedora.taila91c66.ts.net:8444/docs/20261021-134612-pr-360-configurable-countries.html

Moves the supported countries from a hardcoded list into the database. Global admins can now turn countries on and off under Platform settings.

Data

• New Country table (code, name, enabled). code is the value already stored on volunteers, chapters and local groups (e.g. UK).
• The migration seeds 32 countries from the old list: the 19 that were live are enabled, and the 13 that were commented out are disabled. It also adds any chapter country missing from that list, so no existing chapter breaks.
• NationalChapter.country is now a foreign key to Country.code. A chapter already maps to exactly one country, so the chapter points at the country row instead of holding a copy of it.
• Data impact: no existing rows change. Volunteer, project and local group country values are untouched. The anonymiser marks the new columns keep.

API

• countries.list (public): every country, enabled or not, so a disabled one still shows its name wherever it is already stored.
• admin.countries.setEnabled: global admins (ADMIN_EMAILS) only.
• Signup, a first-time profile country and transfer requests only accept enabled countries (or Other). People who already gave a disabled country keep it.
• Accepting a local group suggestion enables its country. So does opening a chapter, and the chapter picker now lists disabled countries too.
• Server-side country names (notifications, the required-actions pool list, new chapter names) now come from the table.

UI

• Platform settings has a new Countries section: one switch per country, and countries with a chapter are marked.
• Every picker (signup, settings, confirm location, chapter move, admin local groups) offers only enabled countries. Displays use the names from the table.
• The list is fetched once per page load and shared through React Query (useCountries). The settings page refreshes it after a toggle. Pages that show a country name wait for the list, so UK never flashes before United Kingdom.

Tests

• Router tests: only global admins can toggle, on and off both work, an unknown code is refused, disabled countries are refused at signup, profile and transfer, and accepting a suggestion or opening a chapter enables the country.
• Component tests: toggling on the platform settings page (including a failed save), the signup picker leaving out disabled countries, and settings still showing a disabled stored country's name.
• e2e (spec 32): a super-admin disables a country and the signup picker stops offering it. Snapshots of the new section checked on desktop and mobile, in light and dark.

Decisions

• "Super-admin" here means global admin. Since national chapters landed, the two are the same check.
• The UI only enables and disables the seeded countries. Adding a brand-new country still needs a migration, because the issue only asked for enable/disable.
• Someone in the holding pool can suggest a local group in any listed country, disabled ones included. That is how a new country gets asked for, and accepting the suggestion enables the country. A chapter still has to exist before a suggestion can be accepted.
• Disabling a country that already has a chapter is allowed. The chapter keeps working; the country just stops appearing in signup pickers.
• maintenance-checklist.md does not exist in the repo, so there was nothing to remove.

Closes #124

🤖 Generated with Claude Code

[railway-app]

🚅 Deployed to the catalyse-pr-360 environment in PauseAI Catalyse

Service	Status	Web	Updated
web	❌ Build Failed (View Logs)	Web	Oct 24, 2026 at 7:34 pm UTC