Office Data and Weave UI — Single Source Configurations
Why This Matters
Before tackling multi-source complexity, you need to understand the single-source variations. The flexibility in how Weave UI maps to location data is what makes the system so configurable — and what makes it important to understand before debugging UI issues.
What You'll Learn
- The simplest setup: 1 database → 1 SyncApp → 1 Weave UI (single tenant, single location)
- How 1 database with multiple locations can map to 1 UI showing all data combined
- How the same setup can be configured to have 1 UI per location (each reception desk sees only their location)
- How a 3-location database can be split into 2 UIs (e.g., UI 1 shows location 1, UI 2 shows locations 2+3)
- Why UI configuration is 'totally up to the office' — Weave doesn't mandate the mapping
Watch Video
Lesson Summary
When an organization has a single data source, the configurations vary by how many physical locations are in that database and how the office wants to view them. The simplest case is 1 database → 1 SyncApp → 1 UI. But a single database can hold data for 3 locations and be configured to show as: one combined UI, three separate UIs (one per location), or any combination (e.g., two UIs where one shows location 1 and another shows locations 2 and 3). All configurations are valid — the office decides.