Skip to main content
When an organization shares more than a handful of hotspots, operational questions become important. This page outlines how larger deployments are intended to work.
This is roadmap. Bulk tools, an organizational dashboard, and dedicated support are not available today. This describes the intended approach. See Product status.

​
Planning a deployment

Before sharing many hotspots, an organization would consider:
  • Scope: how many hotspots, at how many locations?
  • Access model: public, limited, or a mix?
  • Naming convention: how to organize and identify hotspots?
  • Responsibility: who manages them day to day?
A little planning up front prevents confusion later.

​
Infrastructure considerations

Linkr is not intended to require special hardware. If your existing Wi-Fi works for your users, it should work for Linkr. Points worth checking:
  • Capacity: can your access points handle additional connections?
  • Bandwidth: is there headroom for shared usage?
  • Isolation: is guest traffic separated from internal networks?

​
Organizing hotspots

Consistent naming keeps a deployment manageable — include location identifiers and an organization prefix. For example:
  • CityLibrary-MainFloor
  • AcmeCorp-Building3-Lobby

​
What’s planned

The intended tooling for scaled deployments includes:
  • Bulk creation of hotspots
  • An aggregate view of a deployment’s hotspots
  • Support options for organizations with complex needs
None of this is available yet.

​
Getting involved early

If your organization wants to help shape organizational support, reach out at support@linkrmap.com.
Organizational deployment follows the same principles as individual contribution — share thoughtfully, configure visibility, and keep hotspots online — just at greater scale.