System links make the technical scope of a demand explicit. Include the applications, infrastructure or platforms relevant to the scenario, then explain their dependencies in the context narrative.
Link existing systems
Open Involved systems → Manage systems, search the available system records, select the relevant entries and choose Add selected. Check the resulting names and references before proceeding with assessment.
Open a linked system in its own module to review its lifecycle, architecture, information classification, recovery requirements, contacts and related third parties. Maintain missing or incorrect inventory data through Systems with the appropriate permission.
Define the actual boundary
Explain which component, environment or data flow is being assessed. A system link alone does not identify whether the concern affects its production environment, a development service or one particular integration.
These links also help readers interpret system-based filtering in the Risks register: a risk's scope comes through its associated demand. Linking a system does not automatically make this demand its completed assessment of record.
Remove an obsolete scope link when the assessment boundary changes. The system remains in the workspace inventory.