Skip to content

Commit e930bcc

Browse files
Update README.md
1 parent da8ce83 commit e930bcc

1 file changed

Lines changed: 45 additions & 11 deletions

File tree

‎msp-onboarding/README.md‎

Lines changed: 45 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -187,21 +187,55 @@ Drop `--demo` for live runs. Sample manifests live in [`samples/`](samples/).
187187

188188
### On-Screen Output
189189

190-
The web workflow surfaces the plan and the run in one place:
190+
The web UI supports all the onboarding workflows defined above:
191191

192-
- **Setup stage**: tenant picker with per-tenant service and region discovery; tenants without an eligible service are set aside with the reason shown.
193-
- **Devices stage**: dense inventory table with CSV import, per-device or bulk subscription mapping, and seat capacity and expiry checks.
194-
- **Preflight review**: every tenant, device, and seat assignment with its validation result, plus an impact ledger of what will and will not run.
195-
- **Inventory add**: editable serial and MAC grid with CSV import, row-level validation, preflight, then per-device results.
196-
- **Live run**: the same review switches to per-device status chips (Writing, Complete, Already satisfied, Failed) and per-tenant progress as the job runs.
192+
1. **Add Devices** – add devices to the GreenLake inventory.
193+
2. **Create Tenants** – create MSP tenant workspaces.
194+
3. **Assign Devices to Tenants** – Assign available devices and subscriptions to selected tenants.
197195

198-
<!-- screenshot: sign-in screen (docs/sign-in.png) -->
199-
<!-- screenshot: devices stage with seat mapping (docs/devices.png) -->
200-
<!-- screenshot: preflight review (docs/review.png) -->
201-
<!-- screenshot: live run results (docs/run.png) -->
196+
The following walkthrough focuses on **Assign Devices to Tenants**. The Add Devices and Create Tenants workflows follow a similar experience.
202197

203-
The **CLI** prints the same plan and per-step results as tables, and masks subscription keys in `list subscriptions`.
198+
#### 1. Select Tenants
204199

200+
Select one or more tenants that you want to include in the assignment.
201+
202+
The tool discovers the applicable service and region for each tenant and identifies any tenants that are not eligible for assignment.
203+
204+
205+
#### 2. Select Devices and Subscriptions
206+
207+
Select the devices to assign and map each device to its destination tenant and subscription.
208+
209+
The UI displays the available device inventory and subscription information, including capacity and expiration details, to help build the assignment plan.
210+
211+
212+
#### 3. Pre-flight Review
213+
214+
Before making any changes, the tool validates the complete assignment plan.
215+
216+
Any validation issues are surfaced before the operation begins so that they can be corrected without making changes.
217+
218+
219+
220+
#### 4. Live Run
221+
222+
After the pre-flight review passes, start the assignment.
223+
224+
The UI transitions from the review into a live execution view, showing progress and status for each device as the assignments are processed.
225+
226+
Results are displayed per device, including completed, already satisfied, and failed operations.
227+
228+
[]
229+
230+
### Other Web UI Workflows
231+
232+
**Add Devices**
233+
234+
Add devices to the GreenLake inventory individually or through CSV import. The UI validates device information before the operation and displays the result for each device.
235+
236+
**Create Tenants**
237+
238+
Create one or more tenants through the web UI. Tenant information is validated before creation, with individual results displayed as the operation completes.
205239
### Report Files
206240

207241
- `GET /api/jobs/{id}/manifest`: exports the confirmed job as a YAML manifest (including subscription keys) that the CLI can `plan` and `run` again

0 commit comments

Comments
 (0)