Device Sprawl: Managing VPN Access for a Growing Team

Every VPN setup starts simple: one laptop, one config file. The trouble begins at scale. A growing team accumulates laptops, phones, the occasional shared office device, and contractors who need temporary access — and without a system, "who has a key to our network" becomes a question nobody can answer confidently.

The failure mode is rarely dramatic. It is usually quiet: an employee leaves and their laptop's VPN config is never revoked because nobody remembered it existed. A contractor's temporary access outlives the contract by months. A phone is lost and nobody is sure whether it still has valid credentials sitting in an app.

Why this needs a system, not discipline

Manually tracking device access in a spreadsheet works until the spreadsheet gets stale, which happens the first time someone forgets to update it — which is to say, quickly. The fix is not "be more careful"; it is a system where every device is a first-class, individually named, individually revocable record, not a shared config file passed around over chat.

How PrivNet models this

Every device in PrivNet is its own entry with its own keypair — there is no shared config file to lose track of. The dashboard shows exactly who has how many active devices against the plan limit, and revoking one is a single click that takes effect immediately, not a ticket to IT. For a team that has outgrown "just email the config file," that structure is the actual fix, not a nice-to-have.