Claim controllers, create virtual assets, and manage existing portfolio entries.
The current Add page contains two separate workflows. Choosing the correct one matters because their ownership and removal behaviour differ.
| Workflow | Use it for | Required information |
|---|---|---|
| Claim controller | Link an already installed controller and its device hierarchy to the company. | Controller serial number and verification code. |
| Create virtual asset | Create a manually managed portfolio object for a supported, creatable node type. | Asset name and asset type. |
Only owners see the global Add menu item. The application validates empty names, missing asset types, serial numbers, verification codes, unknown controllers, invalid codes, and claim-rate limits before changing the portfolio.
Claiming is different from creating
A claimed controller retains its controller-managed hierarchy. A virtual asset receives a generated custom-… identifier and starts without children or telemetry streams until these are configured separately.
The two forms are deliberately separate because they create different ownership and hierarchy relationships.