Problem
The Manager UI allows modifying attributes of assets that belong to linked Gateways.
However, the backend rejects these changes. When users try to save, they get a generic "Failed to save asset" snackbar message.
This creates a confusing UX because the UI suggests the action is allowed, while the backend silently prevents it.
Current behavior
- User can click "Modify" and change attributes
- On save, request fails
- Snackbar shows: "Failed to save asset"
- Backend logs:
04/02/2026 15:41:10 INFO ASSET Cannot directly add or modify a descendant asset on a gateway asset, do this on the gateway itself: Gateway ID=5QTaMlUSfjO0pC8TuZSECx
04/02/2026 15:32:31 INFO ASSET Cannot directly add or modify a descendant asset on a gateway asset, do this on the gateway itself: Gateway ID=5QTaMlUSfjO0pC8TuZSECx
Expected behavior
Users should not be able to modify these assets from the Manager UI.
Proposed solution
Disable the "Modify" button for assets that are descendants of a linked Gateway.
Optionally:
- Show a tooltip explaining: "This asset is managed via its gateway"
Steps to reproduce
- Open Manager UI
- Navigate to an asset under a linked Gateway
- Click "Modify"
- Change any attribute
- Click "Save"
- Observe failure snackbar

Impact
- Confusing UX
- Wasted user effort
- No clear indication why the action is not allowed
Problem
The Manager UI allows modifying attributes of assets that belong to linked Gateways.
However, the backend rejects these changes. When users try to save, they get a generic "Failed to save asset" snackbar message.
This creates a confusing UX because the UI suggests the action is allowed, while the backend silently prevents it.
Current behavior
Expected behavior
Users should not be able to modify these assets from the Manager UI.
Proposed solution
Disable the "Modify" button for assets that are descendants of a linked Gateway.
Optionally:
Steps to reproduce
Impact