johannes
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.2 KiB
2.2 KiB
module, title, tab, order, audience
| module | title | tab | order | audience |
|---|---|---|---|---|
| fleet.modules | Modules | Testing | 35 | internal |
Frontend test checklist for the Agent Modules screen (fleet.bcos.dev). This screen is a read-only reference catalog — there is nothing to create, edit, or delete. Click through in the UI and mark each row Pass or Fail.
Set up
Log in at fleet.bcos.dev — test accounts (all password Passw0rd-d3v!):
| Login | Role | Sees |
|---|---|---|
bcos_a@bcos.dev |
Admin | All institutions |
msp_a@msp1.bcos.dev |
MSP admin | C1 + C2 only |
customer_a@customer1.bcos.dev |
Customer | C1 only · read-only |
The module catalog is the same fixed list for everyone — it is not filtered by institution or device, so you won't need specific simulators (C1-ATM-001…) here.
What to test
| # | Do this | ✅ Pass if |
|---|---|---|
| 1 | As msp_a, open the Modules screen from the Fleet menu |
Page loads with the heading Agent Modules and a short description line under it |
| 2 | Scan the section headings | You see four category sections in order: Data Collection, Monitoring, Fleet Management, Updates — each with an icon |
| 3 | Count the module cards across all sections | There are 16 cards total (Data Collection 7, Monitoring 3, Fleet Management 4, Updates 2) |
| 4 | Look at any single card (e.g. Journal Events) | It shows a bold display name, a small grey code chip beneath it (e.g. journal-events), and a plain-language description sentence |
| 5 | Check the status counts on the cards | Cards render cleanly with no running / disabled / failed badges — this is expected right now, so empty badges are a Pass, not a fail |
| 6 | Look for any action controls on the screen | There is no Add / Create / Edit / Delete button anywhere — the screen is view-only |
| 7 | Log in as customer_a, open the Modules screen |
You see the same 16 modules in the same 4 categories, still with no Add button (read-only catalog, not scoped to C1) |
| 8 | Log in as bcos_a, open the Modules screen |
The same full catalog loads with no error — the list does not change by role |
Report a fail with: the row #, which login you used, and what you actually saw.