Layers, namespaces and settings
Layers
A layer is organisation, not protection: nodes are spread across layers, a layer can be hidden or shown, reordered, renamed. The layer order is shared by the team; local visibility toggles are yours alone and do not bother neighbours. Rights on a layer are granted separately in the cabinet, see the teams chapter.
Namespaces
Every node has a key of the form namespace::id. The default namespace is global; imported languages and code parses live in their own namespaces, so keys never collide. A namespace can receive a grant just like a layer.
Groups
A group holds children and drags with them. Dropping a node onto a group makes it a child; moving its centre out of the frame takes it back out. A particular group can be set to grow to fit and to lay its children out on a grid.
App settings
- Grid and snapping: grid step, snapping while dragging, arrows move by a grid step.
- Theme: dark and light, interface scale.
- Server: address and port for the desktop app; without a server it starts an embedded one and keeps data in the system app folder.
- Site: the sign-in site address for desktop and self-host.
- Data flow preview: highlighting values on edges.
History and snapshots
Undo and redo inside a session. The server keeps a history of workspace snapshots: Workspace → History shows them and rolls back to any. A snapshot is taken after an import, on schedule and on request.
Bundles, import and export
The whole workspace exports as one JSON with nodes, edges, types and layers and imports into another instance. Mermaid, PlantUML and SVG import, a PNG snapshot of the scene. Importing the same bundle again does not count as an edit; import rights equal edit rights.