Admin and Governance (User Perspective)
This chapter explains what each admin area controls and how those settings affect daily users.
For step-by-step creation procedures (ISGL, ad hoc case genes, users, roles, ASP, ASPC), use:
For developer-sensitive schema and permission internals, use:
Admin entry point
What each admin section controls
Users (/admin/users)
Controls:
- who can log in
- assay and environment scope
- explicit allow/deny permissions
- active/inactive state
Impact on analysts:
- visible samples are constrained by assigned assays/environments
- route access changes immediately after permission updates
Roles (/admin/roles)
Controls:
- permission bundles
- role levels and labels
Impact on analysts:
- baseline access to workflow pages and actions
Permissions (/admin/permissions)
Controls:
- fine-grained route/action permissions
Impact on analysts:
- determines whether actions like classify, hide comments, or create reports are available
Schemas (/admin/schemas)
Controls:
- dynamic form definitions for managed entities
Impact on operations:
- incorrect schema edits can break admin create/edit forms
ASP: Assay Specific Panel (/admin/asp/manage)
Controls:
- panel metadata
- covered genes and germline genes
- assay family/category descriptors
Impact on interpretation:
- effective gene baseline for sample analysis
ASPC: Assay Specific Panel Config (/admin/aspc)
Controls:
- filter defaults
- analysis/report sections
- report headers/paths
- CNV thresholds and other assay behavior
Impact on interpretation:
- what appears on DNA/RNA pages
- report content and structure
ISGL: In Silico Gene List (/admin/genelists)
Controls:
- curated gene lists with assay/assay-group linkage
Impact on interpretation:
- selectable gene filters on sample settings
- effective gene set used during review/reporting
Samples management (/admin/manage-samples)
Controls:
- sample-level admin edit/delete flows
Impact on analysts:
- sample metadata/state corrections
Audit (/admin/audit)
Purpose:
- operational trace of user/admin actions
Governance best practices
- Change one config domain at a time (roles, permissions, ASP, ASPC, ISGL).
- Validate with a smoke sample after every change.
- Prefer role-based permission design; keep per-user overrides minimal.
- Keep config history and rollback intent documented.