Feature request: Lock / freeze services or groups on the Canvas to prevent accidental moves
gitnexgenmx
PROOP
5 months ago
Hi Railway team — I’d like to request a feature for the Canvas: the ability to lock the position of a service and/or a group of services so they can’t be dragged accidentally.
Problem / Why this matters
We use Railway in a collaborative workflow (multiple people editing the same project). Right now, services/groups on the Canvas are very easy to move by mistake (click + slight drag), and over time the layout becomes messy and inconsistent. This happens more often when switching between different browsers/devices/users, where small accidental movements cause the Canvas to drift and get disorganized.
Steps to reproduce
- Open a project with multiple services on the Canvas.
- Have multiple teammates open the same project in parallel (or switch between browsers).
- Click around to inspect services, connect services, or pan/zoom.
- A small mouse movement can drag a service/group unintentionally.
- The Canvas layout becomes progressively disordered.
Expected behavior
- Users should be able to lock a service or a group so it cannot be moved until explicitly unlocked.
- Ideally, locked items also can’t be nudged by keyboard shortcuts (if any) and are protected from accidental repositioning.
Proposed solution (one possible UX)
- Add a “Lock position” toggle:
- Per service (right-click context menu / service settings)
- Per group/selection (select multiple → “Lock selection”)
- Visual indicator when locked (e.g., small lock icon + disabled drag cursor).
- Optional: a Canvas-level mode like “Edit layout” vs “View only” to reduce accidental changes.
- Optional permissions:
- Lock/unlock restricted to project owners/admins, or
- Lock state stored with the project so everyone sees the same locked layout.
Additional notes
- The biggest pain is accidental layout drift, not intentional rearranging.
- A lock would keep the Canvas readable and stable for teams, especially across browsers.
Thanks!
0 Threads mention this feature
0 Replies