Protect important Flowgen cards without preventing movement, editing, wiring, or running them.
Where: Node or group → lock toggle, or the canvas selection/context menu → Lock / Unlock.
Key ideas
- A narrow protection: A lock prevents deletion and cutting. It does not freeze a card’s position, stop execution, prevent rewiring, or make its contents read-only. Use it to protect a useful source or group from accidental removal while continuing work.
- Groups and descendants: Deleting a group also deletes its interior, so a locked descendant can veto removing that group. Locking the group itself does not individually lock every child: an unlocked child can still be removed on its own.
- Local canvas behavior: Duplication on the same canvas inherits the lock. Exported group assets, blueprints, and marketplace payloads clear local locks, and paste-in clears them as well so recipients do not inherit undeletable cards.
Steps
- Select the node or group you want to protect and enable its lock toggle.
- Continue moving, editing, wiring, or running it as needed; those actions remain available.
- If deletion or cut is refused, read the named locked card in the message. For a group, inspect descendants as well as the group frame.
- Unlock the actual protected card only when you intend to remove it, then retry the removal.
- When sharing or exporting a reusable graph, expect its recipients to choose their own locks rather than receiving yours.
How mixed selections behave
A removal request is evaluated by its selected roots and the nodes each removal would actually take. Allowed roots can proceed while protected roots are refused. The same rule covers keyboard deletion, context actions, cutting, and group removal instead of protecting only one gesture.
Area frames are different
An area frame whose deletion keeps its children does not need a locked child to veto removing the frame. Cutting is different because it removes the subtree; that path uses the stricter protection. This distinction prevents a locked card from trapping a harmless surrounding area frame.
Tips
- Lock stable reference inputs before large graph cleanup.
- Use the reported card name to find the protection; repeated Delete presses do not override it.
Limitations and important notes
- This is accidental-removal protection, not an access-control or immutability feature.
Troubleshooting
A locked node still moves or runs.
That is expected. Lock protects delete/cut only.
A group cannot be deleted even though its own lock is off.
Look for a locked descendant that would be deleted with it. Unlock that descendant deliberately or move it outside the group first.