Company Network Maps

Network Maps give each company an interactive Leaflet map where you can manage sub-locations, place building and device markers, link markers to existing assets and NinjaOne devices, attach photos, protect gate codes, and overlay georeferenced floor plans.

Opening a map

1. Open Tools in the sidebar and click Maps, or open a company and choose the Map tile under Company Data.
2. Pick a company from the searchable list or selector. The map centers on the selected sub-location, primary sub-location, company address, or existing markers.
3. Use the map search box to jump to an address or GPS coordinate.

Street and satellite basemaps are available from the map toolbar. When your workspace is in dark mode, the street basemap switches to a dark style and marker popovers match your theme so labels and action buttons stay easy to read.

Company sub-locations

Company pages include a Locations section under Customer Information. Add each campus, building group, or unrelated address there with either an address or coordinates. Maps use those records for the location selector and zoomed-out location markers.

Markers

• Choose a marker type (switch, access point, mesh node, gateway, camera, server, printer, building, map label, entrance/gate, or custom) from the Add marker menu, then click the map to drop it.
• Drag any marker to reposition it. Changes save automatically.
• Open a marker to rename it, change its type, assign it to a location, building, and floor, add notes, link an asset or NinjaOne device, and attach photos. On supported mobile browsers, photo upload opens the device camera.
• Entrance/gate markers use a square icon. Gate codes are stored as protected technician notes and can be revealed from the map by users with secrets:read.

Hierarchy and filtering

Maps follow the hierarchy company → sub-location → building → device. Zoomed-out maps show location markers; closer views show building markers; close building views reveal child devices. The left sidebar supports keyword search, device type filtering, and grouped building/device lists. Floor filters apply to markers and overlays. Nearby markers combine while zoomed out, then separate as you zoom in.

Floor-plan overlays

• Use Add overlay to upload a floor-plan image. It is placed over the current viewport and inherits the active location/floor.
• The Layers panel controls per-overlay opacity and visibility. It also lets you nudge, resize, or remove overlays.

Importing legacy maps

Use Import JSON to load an existing network-mapper export ({ clientName, devices: [...], buildings: [...] }). Markers with valid coordinates are imported and the company is centered on them; entries with unparseable coordinates are skipped and reported.

Permissions

Network Maps are governed by the maps:read, maps:create, maps:update, and maps:delete permissions and are fully tenant-isolated through Row-Level Security. Gate-code reveal additionally requires secrets:read; gate-code changes use protected technician notes so secret content is excluded from audit diff payloads while reveal events are still audited.

Company Network Maps

Network Maps give each company an interactive Leaflet map where you can manage sub-locations, place building and device markers, link markers to existing assets and NinjaOne devices, attach photos, protect gate codes, and overlay georeferenced floor plans.

Opening a map

1. Open Tools in the sidebar and click Maps, or open a company and choose the Map tile under Company Data.
2. Pick a company from the searchable list or selector. The map centers on the selected sub-location, primary sub-location, company address, or existing markers.
3. Use the map search box to jump to an address or GPS coordinate.

Street and satellite basemaps are available from the map toolbar. When your workspace is in dark mode, the street basemap switches to a dark style and marker popovers match your theme so labels and action buttons stay easy to read.

Company sub-locations

Company pages include a Locations section under Customer Information. Add each campus, building group, or unrelated address there with either an address or coordinates. Maps use those records for the location selector and zoomed-out location markers.

Markers

• Choose a marker type (switch, access point, mesh node, gateway, camera, server, printer, building, map label, entrance/gate, or custom) from the Add marker menu, then click the map to drop it.
• Drag any marker to reposition it. Changes save automatically.
• Open a marker to rename it, change its type, assign it to a location, building, and floor, add notes, link an asset or NinjaOne device, and attach photos. On supported mobile browsers, photo upload opens the device camera.
• Entrance/gate markers use a square icon. Gate codes are stored as protected technician notes and can be revealed from the map by users with secrets:read.

Hierarchy and filtering

Maps follow the hierarchy company → sub-location → building → device. Zoomed-out maps show location markers; closer views show building markers; close building views reveal child devices. The left sidebar supports keyword search, device type filtering, and grouped building/device lists. Floor filters apply to markers and overlays. Nearby markers combine while zoomed out, then separate as you zoom in.

Floor-plan overlays

• Use Add overlay to upload a floor-plan image. It is placed over the current viewport and inherits the active location/floor.
• The Layers panel controls per-overlay opacity and visibility. It also lets you nudge, resize, or remove overlays.

Importing legacy maps

Use Import JSON to load an existing network-mapper export ({ clientName, devices: [...], buildings: [...] }). Markers with valid coordinates are imported and the company is centered on them; entries with unparseable coordinates are skipped and reported.

Permissions

Network Maps are governed by the maps:read, maps:create, maps:update, and maps:delete permissions and are fully tenant-isolated through Row-Level Security. Gate-code reveal additionally requires secrets:read; gate-code changes use protected technician notes so secret content is excluded from audit diff payloads while reveal events are still audited.