Subscription and Site Scoping for a Multi-Campus University
Northvale University runs one Mist organization for three campuses: Main, North, and South. Inventory is 480 APs and 110 switches serving about 6,000 daily clients. The organization owns 500 wireless subscriptions, 120 wired subscriptions, and 150 Marvis subscriptions. Today Main is assigned 300 APs, 70 switches, and 100 Marvis; North has 100 APs, 25 switches, and 30 Marvis; South has 80 APs, 15 switches, and 20 Marvis. The university is opening West campus with 55 APs, 12 switches, and a small IT team. West APs have been claimed successfully, but the West site shows no Marvis insights, and several West technicians can currently see and edit all campuses. The CIO wants West isolated from an administration standpoint without fragmenting inventory, templates, or reporting. A quarterly subscription renewal is two weeks away.
1. Calculate the subscription position for the fourth campus and decide what to request in the renewal. Explain the order of operations.
Read the worked answer
Start by comparing total inventory plus West against owned entitlements, not against what is currently assigned. Wireless: 480 existing APs + 55 West APs = 535 needed versus 500 owned, a shortfall of 35. Wired: 110 + 12 = 122 needed versus 120 owned, a shortfall of 2. Marvis: the 150 subscriptions are already allocated across Main, North, and South, so West currently has no Marvis entitlement. Do not solve this by moving AP subscriptions away from production sites; that only hides the gap. Request 35 wireless, 2 wired, and enough Marvis for West in the renewal. If procurement cannot complete before opening, prioritize assigning Marvis to West only after confirming whether the entitlement is consumed per site or by device count, and document the temporary gap. Keep the new devices in the same organization so inventory, templates, alarms, and reporting remain unified.
2. How should administrative access be scoped for West, and why is a second organization a poor choice?
Read the worked answer
Use site-scoped administrative roles rather than a new organization. In Mist, an administrator can be granted access to specific sites; the West IT group should receive a role limited to the West site, while the central team retains org-level visibility. If the university uses SSO, map an IdP group for West staff to the site-scoped role so joiners and leavers are handled centrally. A second organization would force duplicate WLAN and RF templates, split inventory and subscription pools, complicate cross-site reporting and Marvis Actions, require separate API tokens and webhooks, and create two SSO integrations. It would also make central troubleshooting harder because an engineer would need to switch organizations to follow a client that roams or a ticket that spans campuses. The only strong reason to split organizations is a hard regulatory or business boundary, which is not present here.