Co-Working WiFi: Crowded Access Points and Members Who Move
In a co-working space, half the room ends up on the access point by the front door, and the other half loses the connection every time they walk to a meeting room. Both problems have real fixes, and they live in two different layers.
Co-working WiFi has two problems that hotel or cafe WiFi rarely has at the same scale. The first is crowding: dozens of members arrive at the same time, and far too many of their laptops and phones end up connected to the same access point, usually the one nearest the entrance, while the access points over the desks sit half empty. The second is movement: a member starts at a hot desk, walks into a meeting room for a call, then carries the laptop to the cafeteria, and the connection stutters, drops, or asks them to log in again on the way. The fixes for these two problems live in different places. Crowding is mostly a radio problem, solved in how the access points are placed and configured. The re-login problem is an identity problem, solved in where the login lives. This post covers both, and is precise about which part Wyfy Guest handles and which part belongs to the access points.
The short answer: members crowd one access point because their devices choose where to connect and rarely switch; access point settings such as band steering and a minimum signal threshold spread them out. Re-login prompts while roaming come from separate networks or WiFi names, and stop once the floor is one network, one name and one login.
Why does everyone end up on the same access point?
Because the laptop decides, not the access point, and laptops are lazy about it.
When a device joins WiFi, it picks an access point, usually the one with the strongest signal at that moment. Then it tends to stay there. Most phones and laptops only look for a better access point once the signal from the current one gets genuinely poor, not merely worse than a neighbour’s. Network engineers call these “sticky clients.”
Now picture a co-working morning. Thirty members walk in through the same door within the same hour. Their devices wake up near reception, see the access point by the entrance as the strongest, and join it. Then everyone walks to their desks, and most of those devices stay attached to the reception access point, because its signal at the desk is still “good enough” by the device’s own standard. The access point over the desks, ten metres away, carries a handful of devices. The one by the door carries most of the room.
Why one crowded access point slows everyone on it
WiFi airtime is shared. An access point’s radio can only talk to one device at a time on a channel, and it takes turns. A laptop at the far end of the room, holding on to a weak signal, talks slowly, so every one of its turns takes longer. A crowded access point with a few distant devices on it ends up spending much of its time on its slowest clients, and everyone else on that radio waits. This is why “the WiFi is slow” in a co-working space so often has nothing to do with the internet line. The line can be half idle while one access point is overloaded. (When the line itself is the bottleneck, that is a different problem with a different check.)
More access points alone don’t fix it
How many access points a space needs is the right first question, and an open-plan floor full of laptops usually needs more density than its square footage suggests. But adding access points does not help if devices never move onto them. A fourth access point that nobody joins is just a more expensive ceiling decoration. The fix is to add coverage and also give devices a reason to spread out.
What actually spreads members across access points?
These are settings on the access points or their controller, not on the login page. Most business-grade access point systems offer some or all of them, and they are worth checking before buying more hardware.
| Setting | What it does | Why it helps a co-working floor |
|---|---|---|
| Band steering | Nudges devices that support both 2.4 GHz and 5 GHz onto 5 GHz | 5 GHz has more channels and more room, so the busy 2.4 GHz band is left for older devices |
| Minimum signal threshold | Disconnects a device once its signal drops below a level you set, so it reconnects to a closer access point | Breaks the “still attached to the reception access point from my desk” pattern |
| Client load balancing | Limits how many devices one radio accepts, or steers new devices to a less busy neighbour | Stops the access point by the door from taking the whole room |
| Fast roaming (802.11r, with 802.11k and 802.11v) | Lets a device learn its neighbouring access points and hand over to one quickly, without a full reconnection | Calls and video meetings survive a walk from desk to meeting room |
| Lower transmit power | Makes each access point cover a smaller area | Devices see a clear “closest” access point instead of several at similar strength |
Two cautions. A minimum signal threshold set too aggressively makes devices bounce between access points, which feels worse than being sticky, so change it in small steps. And fast roaming is not supported by every older device, so test it with the laptops your members actually carry before turning it on everywhere.
These settings live on the access points and their controller, and the right values depend on your hardware and your floor. You do not have to tune them yourself: when we set up Wyfy Guest at your space, our team configures band steering, the signal threshold, load balancing and fast roaming on your access points, then checks them against your layout.
Why do members get asked to log in again when they move?
When a member walks from a desk to a meeting room and gets a login page again, the cause is almost always one of two network design mistakes, not the movement itself.
The access points are separate networks
The most common cause in smaller spaces is consumer routers used as access points, each running in its own router mode. Each one hands out its own addresses. When a laptop moves from one to the next, it gets a new address on a different network, and to the login system it looks like a brand-new device that has never signed in. The fix is to run every access point as a plain access point on one shared network, with one gateway handing out addresses for the whole floor.
Each area has its own network name
The second cause is a different WiFi name per area: “Cowork-Desk”, “Cowork-Meeting”, “Cowork-Cafe”. A laptop treats each name as a separate network, and switching names is a full disconnect and reconnect every time. Modern phones and laptops also use a separate private hardware address for each network name, so to the login system a device on “Cowork-Cafe” can look like a stranger even though it signed in on “Cowork-Desk” an hour ago. Use one network name across the whole space, so moving between access points is a handover rather than a fresh join.
Once both are right, roaming between access points is invisible to the login system. The device keeps its address and stays on the same network the whole time.
How Wyfy Guest keeps one login across the whole floor
This is the part that is Wyfy Guest’s job, and it is designed around one idea: a member’s login belongs to their device on your network, not to whichever access point they happened to be near when they signed in.
The login lives at the gateway
Wyfy Guest works with the venue’s router or WiFi controller, the device that sits in front of every access point, rather than with any single access point. The branded login page is served through that gateway too. When a member signs in, the session is recorded against that member, that venue’s gateway, and that specific device. Walking from the hot desk to the meeting room to the cafeteria changes which access point carries the signal. It does not change any of those three things, so there is nothing to sign in to again.
A dropped connection doesn’t mean a new code
Laptops sleep, lids close, and WiFi gets switched off and on. When a device comes back and the login page reappears, Wyfy Guest’s login page first checks whether that device still has a live session at this venue. If it does, the member is put straight back online instead of being asked for a fresh OTP. For the next day’s visit, a venue can also let members set a password on the login page, so a returning member signs in without waiting for a code to arrive.
The limits follow the member, not the access point
Because the limits are applied at the gateway, they hold wherever the member sits:
- Per-member speed limit. A download and upload cap for each person, so one member syncing a large backup cannot take the whole internet line. Per-guest speed and session limits explains how to set one. Be clear about what it does: it shares the internet line fairly. It does not add radio capacity to a crowded access point. That still needs the settings in the table above.
- Devices per member. Each member can be limited to a set number of devices, three by default. A member with a laptop, a phone and a tablet fits. A fourth device does not quietly join. This matters on a crowded floor, where every member brings at least two devices.
- Idle timeout. A device that stops sending traffic for a set time, thirty minutes by default, is signed out, so a laptop that went home in a bag stops holding one of its owner’s device slots. Match the value to how your members work. Too short, and someone back from a long lunch has to sign in again.
- Session length. How long one sign-in lasts before the member is asked again. The default is four hours. A space where members stay all day may want it longer.
Which of these a venue can enforce depends on the router or controller it runs, so confirm it for your own hardware before you plan around one.
Teams, not just individuals
Many co-working members are part of a company that rents a block of desks. Guest Groups let you manage that company as one team with its own shared allowance, instead of forty separate members. Guest WiFi for co-working spaces covers teams, day passes and reports in more detail.
How do you know which access point is the problem?
You need two kinds of visibility, and they come from two places.
From Wyfy Guest, you get the people side. Live Sessions shows who is online right now. You can also register each access point by its hardware address as monitored network hardware, and the dashboard shows it as up, down, or not yet seen, based on what your router actually observes on the network, where the venue’s router supports that check. That answers “is the access point in the meeting room even on?” without walking over to look. Visibility beyond the router explains how that works.
From the access point controller, you get the radio side: how many devices each access point is carrying, which band they are on, and how strong their signal is. That is where you will see the access point by the door carrying most of the room. Wyfy Guest does not show per-access-point device counts or signal strength, so for that question, the controller is the place to look.
Common questions about co-working WiFi roaming
Does Wyfy Guest do band steering or fast roaming?
Yes, we set it up for you. Band steering, minimum signal thresholds, client load balancing and fast roaming (802.11r, 802.11k and 802.11v) run on the access points and their controller, and our team configures them during setup. Wyfy Guest then handles the login, the per-member limits and the session, so a member who roams between access points stays signed in.
Why does a member have to log in again after walking to a meeting room?
Almost always because the meeting room is on a different network: either its access point is a consumer router running its own addresses, or it broadcasts a different WiFi name. Either way the device arrives as a new client. One shared network behind one gateway, with one WiFi name, removes the prompt.
Will members have to enter a new OTP after their laptop sleeps?
Not while their session is still live. When the login page opens, Wyfy Guest first checks whether that device already has an active session at the venue and, if it does, puts the member straight back online. A new code is only needed once the session has ended, for example after the idle timeout or the session length.
How many people can one access point handle in a co-working space?
There is no fixed number. A commonly cited planning range is 25 to 50 connected devices per access point, and a co-working floor reaches that faster than its headcount suggests because every member brings two or three devices. How many access points you need covers sizing in more detail.
Does a per-member speed limit fix a crowded access point?
No. A speed limit shares the internet line fairly, so one large upload cannot slow everyone else. It does not add radio airtime to an overloaded access point. That needs more access points in the right places and the steering settings described above.
A practical checklist for a co-working floor
- Run every access point as a plain access point on one shared network, behind one gateway. No consumer routers in router mode.
- Use one WiFi name across the whole space.
- Place access points where members actually sit and meet, including meeting rooms with closed doors, not just where the cabling was easiest.
- On the access points, turn on band steering, then try a mild minimum signal threshold and client load balancing. Test fast roaming with your members’ own laptops before enabling it everywhere.
- In Wyfy Guest, set a per-member speed limit, a device limit and an idle timeout that match how your members work.
- Register your access points as monitored hardware, so you know when one goes down before a member tells you.
- When someone says “the WiFi is slow,” check the access point controller for a crowded radio before blaming the internet line. Troubleshooting guest WiFi login problems covers the cases where the login itself is the issue.
Done together, these fix both halves of the problem. The access points spread the room so no single radio carries everyone, and the login stays with the member’s device, so walking to a meeting room is just walking to a meeting room.