Use multi-select on the Asset Dashboard to deploy several in-inventory devices to one employee in a single order. Pick the assets, pick the person, review, and submit once instead of repeating the Assign flow for every device.
What's new
- Checkboxes on the assets table — the single-choice radio column is now a checkbox column, so you can select more than one asset at a time
- Selection bar — a bar appears at the bottom of the table showing how many assets are selected, with an Assign button and Clear selection
- One order, many devices — the employee selection and checkout pages carry every selected asset, and submission creates one deployment order with one line per asset
- Remove at checkout — drop an asset from the order in the review table without starting over
Before you start
- Every asset you plan to select must show the status In Inventory
- Every asset must be held in the same depot
- Know which employee should receive the devices — one order goes to one person
Step 1 — Select assets
- Open the Asset Dashboard
- Tick the checkbox on each asset you want to deploy
- The selection bar appears showing the count, for example 3 assets selected
- Page through, sort, or filter as needed — your selection is kept as you move around the table
Tip: the header checkbox selects only the assets on the current page. To build a larger set, select page by page or narrow the table with filters first.
Step 2 — Click Assign
- Assign is enabled when every selected asset is In Inventory and all share one depot
- The button stays disabled while eligibility is being checked, and if any selected asset does not qualify
- If Assign is greyed out, look for an asset in another status or a different depot and clear it from the selection
Step 3 — Choose the employee
- The top of the Assign Device page shows a summary of what you are deploying, for example 3 assets: 2 Laptops, 1 Monitor
- Select the destination country if prompted
- Search for and select one employee
- Click Continue
Step 4 — Review and submit
- Asset Review lists one row per asset with make, model, type, serial number, and asset number. Click Remove on any row to drop it from the order
- Recipient — confirm the employee's email and shipping address
- Shipping & Insurance — choose shipping and insurance. Insurance applies to the whole order, not per device. Add a billing reference or order notes if your org uses them
- Click Submit. One order is created and each asset moves to Pending Allocation
Known limitations
- Multi-select applies to Assign only. Process, Repair, Recycle, Resell, and other device actions still work on one device at a time
- In Inventory only. Assets in HOLD, In inventory - device issue, or any other status cannot be included. A single ineligible asset disables Assign for the whole selection
- One depot per order. Assets in different depots must be deployed in separate orders
- One employee per order. To deploy to several people, create one order per person
- Select all is per page. The header checkbox selects only the rows currently visible
- Selection is cleared when you leave the Asset Dashboard. Navigating away and back starts a fresh selection
- Up to 100 assets per order. Larger deployments should be split into multiple orders
- The last asset cannot be removed at checkout. An order needs at least one device. To change the only remaining asset, cancel and start again from the Asset Dashboard
- Insurance is order-level. You cannot insure some devices in the order and not others
If something goes wrong at submission
- An asset's status changed since you selected it — you will see a message naming the asset and its current status. Remove that asset from the review table and submit again
- The order was not created — your selection is kept, so fix the issue and click Submit again without reselecting
- Before retrying, refresh the asset statuses shown in the review table. If a device already shows Pending Allocation, it may have been reserved by the earlier attempt
Single-device deployment
Nothing changes when you select one asset. Assign opens the same flow as before, and existing links to single-asset deployments continue to work.