Integration: Cross-Property Data Isolation and Links

  Property: ChurchWiseAI   Category: API / Integration Tier: all Persona: devops Touchpoint: all domains and their interlinks

Preconditions

• All 3 properties deployed
• Cross-property URLs and integrations configured

Steps

#	Action	Expected Result
1	Verify PewSearch can upsell to CWA	PewSearch admin shows 'Add Voice Agent' CTA. Link goes to churchwiseai.com onboard.
2	Verify ITW can upsell to CWA	ITW admin shows 'Automate Your Sermon Posts' link. Goes to sermonwise.ai.
3	Verify CWA mentions PewSearch integration	CWA docs reference PewSearch directory sync. Both platforms aware of each other.
4	Check customer data isolation	CWA customer can't see PewSearch data. Supabase RLS prevents cross-property access.
5	Verify no shared customer sessions	Logging in to CWA doesn't log you into PewSearch. Separate auth contexts.
6	Check Stripe account isolation	CWA Stripe products different from PewSearch. Charges go to correct org account.
7	Verify analytics don't mix	CWA analytics show only CWA data. PewSearch analytics separate. No data leakage.

Known Failure Modes

• Customer data leaks across properties — privacy breach
• Shared session — customer logged into both — confusing
• Shared Stripe — charges go to wrong account — money missing
• Shared analytics — metrics inaccurate

References

• Playwright spec: e2e (multi-property validation)
• Code files:
  • src/middleware/multi-property-auth.ts
  • src/lib/property-router.ts
  • supabase/rls-policies.sql

Notes

Tests that each property is properly isolated. Shared infrastructure (Supabase, Stripe) is efficient, but data MUST be segregated. Failures mean data breaches or money routing errors. Run after any shared infrastructure change.