LocationId, SourceId, and SourceTenantId Explained
Why This Matters
These three identifiers are the vocabulary of the Integrations team. You'll use them in every WAM session, every ticket description, and every team conversation. Having a clear definition for each is non-negotiable.
What You'll Learn
- LocationId: the unique ID assigned to an entire organization when onboarded to Weave
- SourceId: the unique ID for each SyncApp instance (one per data source per organization)
- SourceTenantId: the most granular ID — one per physical location per data source
- How these three IDs relate: 1 LocationId → N SourceIds → M SourceTenantIds per source
- How data in Weave is always stored and queried by SourceTenantId
Watch Video
Open in Google Drive
💡 Open in Drive for AI-powered transcript search and summaries
Lesson Summary
Three identifiers form the core vocabulary: LocationId identifies the entire organization (assigned at onboarding, maps 1:1 with a WAM account). SourceId identifies each SyncApp instance — one per data source, so one organization can have multiple SourceIds. SourceTenantId is the most granular: one per physical location per data source. Data in Weave is always stored against a SourceTenantId. The Weave UI allows offices to select which SourceTenantIds to display, giving flexible configuration over what each UI shows.
Key Concepts
LocationId
SourceId
SourceTenantId
Identifier Hierarchy
Data Storage Granularity
Weave UI Configuration
Key Takeaways
01LocationId = organization-level identifier (1 per customer)
02SourceId = SyncApp-level identifier (1 per data source, multiple possible per organization)
03SourceTenantId = location-level identifier (most granular, 1 per physical location per source)
04All data in Weave DB is indexed by SourceTenantId — this is the key you'll use most often
05When reading logs or querying data, always know which SourceTenantId you're working with