Multi-tenant offices: a VLAN and WiFi keys (xPSK) per tenant
The landlord runs one set of access points for the whole building. Each tenant's staff sign in with their own company account, building plant runs on WiFi keys, and lobby visitors use the captive portal.
Phones, laptops, tills, CCTV and TVs join through your access point. Cloud RADIUS checks each one and sends it to the open, secure or xPSK network by identity, each on its own VLAN; a leaver whose account is disabled is rejected.
Cloud RADIUS sends every device to the open, secure or xPSK network by identity, each on its own VLAN.
The problem
One building, many companies, and plant that runs all night
Landlords now install the access points; tenants still own their people and their security policy.
Tenants will not share a LAN with the floor below
A tenant's security team asks, before the lease is signed, who else can reach its printers. Cabling a separate network per floor is the old answer.
HVAC, access control and lifts sit on the same air
Building controllers rarely support 802.1X, and a controller on a tenant's network is a route into the building and into the tenant.
Leases end, and access lingers
When a tenant hands back a floor, its printers, keys and contractor access should end that day, without touching anyone else.
The solution
Three networks for a building with many tenants
The landlord owns the radios and the plant; each tenant keeps its own identity and gets its own VLAN or role.
Open
The lobby and the first morning
One building portal for visitors, and an onboarding lane for a new tenant's staff.
- Lobby visitors and meeting guestsOnline until the session times out
- Tenant employees on laptops and phonesFollows the tenant's own leaver process
- One captive portal in the building's brand
- Tenant staff onboarded without the landlord's MDM
Secure
The tenant's identity, the landlord's radios
Cloud RADIUS returns each tenant's VLAN or role from that tenant's own directory groups.
- Managing agent and facilities staffDisabled centrally, off every building
- Tenant staff who come in every dayProfile installed on day one
- Each tenant's directory decides its VLAN
- SecurePass, built on Passpoint, for returning users
xPSK
Plant and tenant kit: a key per controller and printer
Building systems and tenant devices that cannot do 802.1X each hold their own key.
- Tenant printers, screens and room kitRevoked on lease hand-back
- HVAC, access control, lifts and meteringCommissioned once, outlives every tenant
- Fit-out crews and plant engineersEnds with the works
- HVAC, access control and lifts kept apart
- Tenant printers and screens on the tenant's VLAN
Visibility and audit
What a tenant's security review asks the landlord
Hand over the VLAN map and the log during lease negotiations.
- Which keys outlived a lease.
- Which building controllers are online, and on which VLAN.
- Whether a tenant's disabled account was refused.
- ISO 27001 and Cyber Essentials Plus: Held by Purple, for the supplier section of a tenant's security review.
Proof
A building-wide service you can put in a lease
The RADIUS SLA is contractual, so the landlord can stand behind the network it sells.
- 80,000+
- venues run on Purple, in 90 countries
- 99.9%
- cloud RADIUS uptime SLA, in your contract
- 99.999%
- uptime, with a 99.9% cloud RADIUS SLA and multi-region failover
- ISO 27001 certified
- Cyber Essentials Plus
- Zero data breaches since 2012
Trusted by
Add-on: Purple Shield
Add protective DNS with Purple Shield
A separate product you add to your Access networks: protective DNS and content filtering, with a policy per VLAN. Free for 30 days.
FAQ
Questions IT leads ask
Who owns what in a multi-tenant building?
The landlord owns the radios, the uplink and the building plant. Each tenant owns its identity: its Entra ID, Okta or Google Workspace decides where its people land, so the landlord never manages a tenant's staff list.
Does each tenant need its own SSID?
No. One xPSK SSID carries every tenant's devices, with a VLAN or role per tenant. 8 to 10 SSIDs use 15 to 25% of channel airtime, which is what a building with an SSID per tenant ends up paying.
How are HVAC, access control and lifts kept away from tenants?
Each controller holds its own MAC-bound key on a building-systems VLAN that no tenant VLAN can reach. If one is compromised, revoke that key and the rest of the plant carries on.
Our buildings have different access point vendors. Does that matter?
No. The WiFi key is iPSK on Cisco, DPSK on Ruckus, PPSK on Extreme and Ubiquiti UniFi and MPSK on HPE Aruba and Juniper Mist, and Purple returns the same tenant VLANs on all of them.
What happens when a tenant hands back its floor?
Revoke the tenant's keys and remove its directory link. Its printers and staff stop authenticating that day, and every other tenant is untouched.
How do visitors get on without a key from IT?
Most use the building portal. A visitor's kit that cannot complete a portal gets a time-limited key from the console or the Purple API, on a VLAN of its own.
Keep exploring
- Purple AccessWhy three SSIDs
- Purple AccessThe xPSK network
- Guide on purple.aiThe multi-tenant WiFi guide
- Purple AccessBuilding plant on IoT keys
- Purple AccessUse case: Contractors and visitors
- Purple AccessUse case: Card payments and compliance
- Purple AccessCoworking and flex space
- Purple AccessCorporate offices
Book a demo: we issue and revoke a key, live
Bring one tenant's printer and a lift controller's spec. We key both onto separate VLANs and revoke one live.
Book a demo
Your live key demo
A Purple network engineer runs it with you.