A deterministic precedence chain — group → location → SaaS plan → global → stock — that governs hundreds of sub-accounts from one Theme Studio with bulk operations.
Theming one location is easy; governing hundreds is not. The agency needed answers to hard questions: what happens when a location has its own theme and belongs to a themed group? What should new sub-accounts look like by default? How do you restyle 60 locations without 60 edit sessions?
I designed a strict, CDN-mirrored precedence chain — group → location's own theme → SaaS plan → global default → stock GHL — so every location's look is always deterministic:
Bundle locations and theme them as one unit. Joining a group deliberately takes ownership (the member's individual config is removed), so there's never a hidden theme waiting to resurface.
Locations are auto-grouped by the GHL SaaS plan they're subscribed to — every “Pro” customer gets the Pro look with zero manual assignment.
The agency-wide fallback for anything unthemed, with a live count of how many locations currently inherit it.
Multi-select locations to apply, duplicate or reset in one round-trip (MongoDB bulkWrite, unordered so one bad ID never aborts the batch) — all from a command center that renders every location as a live miniature of its actual effective theme.
The studio loads 500+ locations in background batches so first paint is instant; filtering, search and sorting never hit the network. Every card preview resolves the location's true effective theme client-side using the same precedence logic the CDN uses — what you see in the studio is exactly what the client sees.
Tell me what you want your GoHighLevel platform to do, and I'll scope it within one business day.
