The Three Portals

For: Anyone confused about which portal to use for what

OpsStrategyPro currently runs three Netlify-deployed portals. Each is for a different audience and contains different content.

VG Portal

• URL: vg-portal.netlify.app
• Audience: VG Home Buyers stakeholders (Randall, Andrew, Shlomo, finance team)
• Contains: Capture Forms (00-10), Work-Order packets, Process Guides, Reference (cost codes, chart of accounts), Reports (actualsboard, PM workbook), Workflow diagrams
• Password: Different from RWP; see RWP/secrets.md
• Source tree: 02_active/vg/published/

BC Portal

• URL: bc-portal.netlify.app
• Audience: Breakthrough ADHD Center reception team
• Contains: Reception Hub, Reference Sheet, Flowcharts, Cards, Training Book
• Password: Different from VG/RWP
• Source tree: 02_active/bc/published/
• Note: Single-engagement design — sidebar collapses everything under one "Reception" group.

RWP Portal (this site)

• URL: rwp-portal.netlify.app (or rwp.opsstrategypro.com once DNS resolves)
• Audience: Randall + future OpsStrategyPro team
• Contains: Skills inventory, How-We-Work conventions, State across active engagements, Weekly Digest, Activity Timeline
• Password: 4Randall!
• Source tree: 02_active/rwp/published/

Why three sites instead of one

• Confidentiality. VG financials shouldn't be visible to BC's reception team and vice versa. Each portal has its own access code.
• Audience-specific surface. A clinician at BC doesn't need to navigate past 87 VG work-order packets to find the reception flowcharts.
• Independent deploys. Each can deploy on its own cadence without affecting the others. A failed VG deploy doesn't block BC.

What if a future engagement starts?

Add a new tenant:

1. New folder under 02_active/<tenant>/ following the engagement convention
2. New tenant config block in portal_index.py
3. New ~/Sites/<tenant>-portal/ git repo
4. New Netlify project pointing at it
5. New entry in the sync daemon's PORTALS dict

See 02_active/rwp/reference/how-we-work/multi-tenant-portal-pattern.md for the full checklist.

Quick comparison

	VG	BC	RWP
Audience	Client stakeholders	Reception team	OSP internal
Sections	7	1 (Reception)	6
Documents	87+	5	growing
Rebuild trigger	Push to portal repo	Push to portal repo	Source change + 30min debounce
Has password	Yes	Yes	Yes