Capability Boundary Matrix
Component Detail
User Interface
medium complexity
frontend
2
Dependencies
0
Dependents
0
Entities
0
Integrations
Description
A declarative UI panel listing functional capabilities that may exist in both Meander and the external portal, allowing admins to mark which system owns each capability. Prevents the overlap and dual data-entry confusion that HLF explicitly flagged as a rollout risk.
capability-boundary-matrix
Sources & reasoning
The implementation notes explicitly require capability boundary declarations to ensure the two systems do not overlap or conflict operationally. A dedicated matrix panel cleanly separates this concern from the credential configuration form.
No source references — this artifact was included based on reasoning alone (see above).
Responsibilities
- Render capability checklist derived from enabled module set
- Allow admins to assign each capability to Meander, external portal, or both
- Persist boundary declarations via Portal Integration Service
- Surface warnings when the same capability is enabled on both sides
Interfaces
renderCapabilityMatrix(orgId, enabledModules)
saveCapabilityBoundaries(orgId, boundaries)
Relationships
Dependencies (2)
Components this component depends on