04 Network workspaces

Document what you know.See how it connects.

Turn equipment records, diagrams, and infrastructure knowledge into local Inventory, rack, topology, map, IPAM, and comparison workspaces.

Palshell Network Racks workspace showing three rack elevations with installed equipment and color-coded cable paths. — Product captureNetwork rack grid

01 From physical to logical

A cable can have a rack face and a network meaning.

Documented rack links can inform logical topology while topology-only overlays remain editable on their own terms.

Connection routing

Palshell logical-topology editor showing firewalls, switches, internet links, and curved connections on a grid. — Product captureLogical topology / curved links

02 Configuration comparison

Two configurations in. Every changed line visible.

Read added, removed, and changed lines side by side without turning comparison into a live device action.

Palshell Configuration Compare showing two device configurations side by side with changed, added, and removed lines highlighted. — Product captureConfiguration compare / synthetic data

03 Local documentation

Five tools. No fake discovery story.

Equipment Inventory

Keep equipment records in one dedicated workspace. Add assets manually or import records from saved API requests and JSON files, then organize them by category, lifecycle status, and site.

Rack & cable records

Arrange equipment faces, map exact ports, and trace selected cables across one rack or a site-scoped grid.

Topology & site maps

Project documented links into logical topology, add overlays, and place network notes on an editable local map.

Manual IPAM

Record VRFs, VLANs, prefixes, and addresses; search locally; and open explicitly linked SSH sessions.

Configuration compare

Compare two pasted or user-selected local configurations in memory with line-oriented, read-only output.

04 Inventory boundaries

Equipment records—not automatic discovery.

Inventory is a dedicated local workspace with deliberate imports, explicit validation, and separate backup behavior.

IMPORTS / USER-TRIGGEREDOne response page at a time.

Imports come from a saved API GET request, a JSON file, or pasted JSON. There is no scheduled polling, background synchronization, or automatic API pagination.

METADATA / RECORDKEEPINGSaved fields do not imply live state.

Lifecycle status is not device health. Site, rack, and owner are text metadata, not automatic links to other workspaces or an identity directory.

LOCAL / SEPARATE BACKUPInventory keeps its own JSON transfer path.

Saved records work offline and use a dedicated Inventory export and restore flow. Inventory is not part of global search or automatic AI context.

Next / session-bound AIAsk about the exact surface in front of you.