Configuration · Centre list & export

Lists every centre the user can administer with its id, name, whether it has a mobile app and which modules are enabled, plus a CSV download.

AreaConfiguration
Routesconfiguration.centers · configuration.centers.index
Centre modulesalways available
Staff levelsroot · admin · manager · weboperator
Modelscenter · country
UI labeltitle.header.configuration.centers / menu.navbar.configuration.centers
Coverage3 use cases · 1 happy · 2 failure

How it works

The center ability separates four concerns: canRead for root/admin/manager/weboperator, canCreate for root/admin only, canUpdate for root/admin/manager/scmanager, and canShowProposal for root/admin/manager. The ‘Modules’ column is the fastest way to see a centre’s feature footprint, which matters because modules decide almost all feature visibility elsewhere.

Use cases

Why someone opens this (3)

  • A group admin auditing which modules each centre has switched on.
  • Creating a new centre during onboarding.
  • Exporting the centre list for a licensing or billing review.

Path map

flowchart LR
    F(["Centre list and export"]):::feat
    F --> H1["Centre list reviewed and exported"]:::ok
    F -.-> X1["Create not permitted"]:::bad
    F -.-> X2["Export fails"]:::bad
    classDef feat fill:#566066,stroke:#566066,color:#ffffff,font-weight:bold
    classDef ok fill:#e3f1ea,stroke:#0d6b42,color:#0d4a2e
    classDef bad fill:#f7e6e2,stroke:#9a2d1c,color:#6e1f13

Happy paths

Centre list reviewed and exported

  1. Admin opens Configuration → Centres.
  2. The list shows each centre with its mobile-app flag and module set.
  3. downloadCSV produces the export.

Failure paths

QA checklist

Tick these off while regression-testing this feature. The boxes are plain Markdown, so progress is visible in git diffs.

  • ✅ Centre list reviewed and exported
  • ⛔ Create not permitted
  • ⛔ Export fails

Implementation


Generated from doc/feature-inventory.json · id config-centers-list · commit 276788ca6