Multi site, acquisitions and different networks

Multi site, acquisitions and different networks

Q: We have multiple sites and different network vendors. Can GuestConnect handle that?
A: Yes. Each customer gets their own GuestConnect instance, and within that instance:

§  You can have multiple sites, each mapped to different wireless backends (e.g. Aruba Central in one location, Meraki in another).

§  Visitors can be issued keys specific to the site they’re visiting.

§  You can choose to standardise SSIDs across sites or run site‑specific SSIDs.

This is especially useful where you’re:

§  Managing a campus with multiple buildings,

§  Running separate corporate vs operational networks, or

§  Acquiring new businesses with their own Wi‑Fi infrastructure.

 

Q: What if we later switch from one Wi‑Fi vendor to another?
A: GuestConnect is multi‑backend:

§  Our integration layer abstracts the vendor differences (e.g. Aruba Central API versions, Meraki, Fortinet).

§  If you move from one supported platform to another, we update the backend connection while you keep the same GuestConnect workflows, portal and visitor experience.

§  You avoid re‑building your guest Wi‑Fi processes every time the network underlay changes.


    • Related Articles

    • Visitor flows, VIPs and exceptions

      Q: Does every visitor have to use a kiosk or QR code to get Wi‑Fi? What about VIPs or longer term guests? A: Not necessarily. The standard flow is kiosk or QR check‑in, but GuestConnect also provides a web portal for authorised staff. Reception or ...

    • Data, logging and investigations

      Q: What logs and reporting does GuestConnect provide? A: GuestConnect provides: § Per‑visitor access history: who was issued which key, for what period, and at which site. § Timestamps aligned with your visitor management system (check‑in and ...

    • Visitor compliance and behavioural change

      Q: How does GuestConnect help us enforce visitor sign‑in policies? A: GuestConnect tightens the link between sign‑in and Wi‑Fi: § If visitors don’t sign in, they don’t get Wi‑Fi – there’s no alternate shared code to “just give them”. § Staff learn ...

    • Technical depth: APIs, Aruba, ClearPass and network design

      Q: Aruba’s APIs and versions keep changing. How do you keep this working reliably? A: Keeping up with Aruba Central versions and API changes is part of the managed service: § We maintain our own API libraries for Aruba, including handling differences ...