Sheet SYN-06 — Network Operations Manual
Sites & Network Mapping
Tenant-defined sites with labels, and the review workflow that confirms which vendor network belongs to which site.
Scope
Sites are the physical places operators reason about. Vendor platforms know networks; Synapse turns those into confirmed site mappings through an explicit review workflow. This guide covers both halves.
The site record
A site belongs to an organization and carries a name, a free-text region, a country code, and an arbitrary set of label key-value pairs. Labels matter beyond description: compliance policies and journeys can scope to every site carrying a label, account-wide, and policy exemptions match on labels too.
Site detail shows the confirmed network count and the device count that resolves through those networks.
The mapping review workflow
After a sync discovers vendor networks, each one starts unmapped. The review page is where an operator resolves that:
- Suggest mappings. A deterministic name matcher runs over every unmapped network and proposes candidate sites. Suggestions are proposals, nothing more.
- Review the queue. Every unmapped or suggested network is listed. Suggested rows show the proposed site; unmapped rows offer a site picker.
- Confirm. The operator confirms a mapping, either accepting the suggestion or choosing a different site. Confirmation is what makes the mapping real.
- Reject. A wrong suggestion is rejected and the network returns to the queue for a manual pick.
The queue shows an explicit all-mapped state once it is clear. An empty queue is the goal state: it means every device in the fleet resolves to a site.
Why confirmation is mandatory
Device-to-site truth drives compliance scope, scoring rollups, and site-scoped traffic views. Synapse never auto-assigns a network to a site without an operator confirming it, because a silently wrong mapping corrupts every downstream answer.