Add umbrella_flag to users table to indicate umbrella access.
Add umbrella_id to organisations table for basic grouping.
Option: Introduce umbrella_organisation_pivot table for scalable, many-to-many mapping.
Pivot Table Example:
umbrella_organisation_pivot
-------------------------------
id
umbrella_id
organisation_id
This allows an organisation to be linked to multiple umbrellas if required in future.
Process Flow
Client logs in.
System checks if umbrella_flag = 1.
If yes → Display umbrella page with all organisations listed as rows.
If no → Display current single-organisation view.
If user has client_admin privileges → orange buttons appear.
Admin Page Changes
Organisation Setup: Add field to assign umbrella (dropdown or text input).
User Setup: Add checkbox for umbrella login. Optionally select umbrella ID if needed.
Update organisation list views to support multi-organisation linking if using pivot table.
Business Impact
No disruption to existing single-organisation clients.
Multi-organisation clients gain an umbrella overview.
Supports future features such as cross-organisation comparisons (e.g., t-tests).
Scalable for larger clients with multiple brands or departments.
Future-proofed if pivot table is implemented.
By the same token I think eventually we should probably have a dashboard section that shows response rate, trend and change. Will help users think about comms strategy and engagement. Could build in to this section some useful AI tips for increasing engagement when low thresholds are hit (eg spacing out emails; feeding back results; arranged meetings to discuss findings, etc) - will add to list doc