Choose the least destructive action that matches the intended portfolio change.
The current device-management code distinguishes visibility changes from structural removal.
| Intent | Action |
|---|---|
| Keep history but hide the asset from normal navigation | Disable Show installation/asset. |
| Keep the asset active but exclude it from the monitored overview | Disable Show in monitored table. |
| Detach a controller from the company | Use Unclaim on the controller site. |
| Delete a manually created virtual asset | Use Delete on an asset whose identifier begins with custom-. |
Visibility and monitoring controls are reversible presentation choices; Delete is a structural action and must be treated separately.
For a controller site, the application identifies the controller role, gathers monitor relations for the complete hierarchy, removes the current company's applicable monitor relations, and removes the company-to-controller management relation. The controller itself is not treated like a custom- virtual asset.
For a manually created asset, the application removes monitor relations for which the current role has management rights. This can immediately remove the asset from the current portfolio.
Confirm dependencies first
Before a structural removal, check users, reports, alarm scopes, public displays, contacts, documents, targets, API references, and historical-data expectations. Prefer a visibility change when the business intent is only to stop day-to-day monitoring.