4f84fc5e80
The 'dev' audience tier was gated via isInternal() (MSP_ADMIN || BCOS_ADMIN), so MSP admins could read developer/architecture content: technical.* and platform.* Overviews, agent-module internals, dev Internal/Overview tabs. Remap 'dev' to isBcos() (BCOS_ADMIN only) in visible(). Retag the 66 Testing docs from 'audience: dev' to 'audience: internal' so MSP keeps them, per Johannes. Result: MSP sees Customer + Internal + Testing (66 modules); loses all Architect/Claude/architecture. BCOS unchanged. Update platform.guide-access to the new model. Closes #18 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.3 KiB
2.3 KiB
module, title, tab, order, audience
| module | title | tab | order | audience |
|---|---|---|---|---|
| msp.module-allocations | Module Allocations | Testing | 35 | internal |
Frontend test checklist for Module Allocations in the MSP admin SPA (msp.bcos.dev). Click through in the UI and mark each row Pass or Fail.
Set up
Log in at msp.bcos.dev and open Module Allocations — test accounts (all password Passw0rd-d3v!):
| Login | Role | Sees |
|---|---|---|
bcos_a@bcos.dev |
Admin | All institutions (C1BD + C2BD + C3BD) |
msp_a@msp1.bcos.dev |
MSP admin | C1BD + C2BD only |
customer_a@customer1.bcos.dev |
Customer | No MSP access |
This screen lists users grouped by institution (C1BD / C2BD / C3BD) — it does not target devices. Use the seeded sim users under each institution.
What to test
| # | Do this | ✅ Pass if |
|---|---|---|
| 1 | As msp_a, open Module Allocations |
Page loads with an Available modules legend at the top and users grouped under institution headings |
| 2 | Click an institution heading (e.g. C1BD) | The group expands/collapses; each user row shows User, Status (Active/Disabled), Email, Current Modules |
| 3 | In the Filters sidebar, type a name or email in Search | The list narrows to matching users, a filter chip appears, and the count pill updates |
| 4 | Set the Institution filter to C2BD, then click ✕ Clear all | Only C2BD users show while filtered; Clear all resets back to every group |
| 5 | Click a user row | A slide-in panel opens on the right listing every module with a name, description and checkbox |
| 6 | Tick a module, click Save Allocations | A success toast appears, the panel closes, and that user's Current Modules now shows the new module icon |
| 7 | Reopen the same user, untick every module, Save Allocations | The row's Current Modules now reads None |
| 8 | Still as msp_a, look at the institution headings |
You see C1BD and C2BD only — no C3BD |
| 9 | Log in as bcos_a, open the screen |
All institutions appear, including C3BD |
| 10 | Log in as customer_a |
The Module Allocations screen is not available (no MSP tile / access denied) — customers can't manage allocations |
Report a fail with: the row #, which login you used, and what you actually saw.