Multi-Location Setup — Real-World Configurations
Why This Matters
Seeing all configuration patterns laid out together gives you a visual taxonomy you can match against real customer setups. This is the reference lesson you'll come back to when facing a complex multi-location ticket.
What You'll Learn
- Six distinct configuration patterns with names (e.g., Single Weave Location / Single Tenant PMS, Multiple Weave Locations / Multi-Tenant PMS)
- What 'single tenant' vs. 'multi-tenant' PMS means in the context of location data
- How Gentrix + Eaglesoft (two different PMSs) can feed into one Weave UI
- The most complex pattern: multiple Weave UIs with mixed single-tenant and multi-tenant PMS sources
- Why 'the number of UIs' and 'the number of PMS sources' are completely independent choices
Watch Video
Lesson Summary
The lesson catalogs six real-world multi-location configurations: (1) Single Weave location + single tenant PMS — simplest setup. (2) Single Weave location + multiple single tenant PMSs — two different PMSs feed one UI. (3) Multiple Weave locations + multiple single tenant PMSs — same as #2 but with separate UIs per source. (4) Single Weave location + single multi-tenant PMS — one PMS with data for many locations in one UI. (5) Multiple Weave locations + single multi-tenant PMS — same PMS, but office chose to split into multiple UIs. (6) Multiple Weave locations + mixed PMS types — the most complex scenario.