Cross-Solution Linkage — One Relational Model Across Every Solution
Connect Records in different Solutions with Linked Record Fields—so risks reference controls, controls reference policies, and every team works from linked data instead of duplicated copies.
What Is Cross-Solution Linkage?
Cross-Solution Linkage is SmartSuite's ability to connect Records across Solution boundaries: Linked Record Fields connect Tables within and across Solutions, with every link mirrored on both sides. It helps GRC, IT, and business operations teams keep one relational data model—risks, controls, policies, vendors, and projects referencing each other instead of drifting apart as duplicated copies. The capability is delivered through the Linked Records Field.
Connected Solutions
Link Records Across Solutions Without Duplicating Data
A Linked Record Field connects Tables within one Solution or across different ones—so the risk register in your Risk Solution links directly to controls in your Controls Solution. Every link is bidirectional: connect two Records and the association appears on both sides automatically.
Fields can allow single or multiple linked Records, and static or dynamic filters narrow which Records are available for selection—keeping cross-Solution connections precise, not free-for-all.
Cross-Solution Data
Pull Lookups, Rollups, and Formulas Across Solution Boundaries
Links carry data, not just references. Lookup Fields display values from linked Records in the other Solution, Rollups aggregate across them—count open findings per control, sum exposure per vendor—and Formulas compute on what comes back.
That turns separate Solutions into one connected model: a compliance dashboard can report on risk data it never stores, because the relationships pull it through live.
Governed Connections
Keep Cross-Solution Links Permission-Aware
Connections respect access control. Members see linked Records only when they hold permission to the linked Table or Solution—so a vendor register can link into a confidential legal Solution without exposing it to everyone who can see the vendor list.
Relationships extend visibility deliberately, never accidentally, which keeps a connected data model compatible with least-privilege access.
Cross-Solution Linkage
GRC data is relational by nature—risks map to controls, controls to policies, findings to audits, vendors to assessments. Cross-Solution Linkage keeps those relationships live even when each register lives in its own Solution.
Link each risk in the risk register Solution to the controls that mitigate it in the controls Solution. Assessors follow the chain in either direction, and coverage gaps show up as risks with no linked controls.
Connect controls to the policies that mandate them in the policy management Solution. When a policy changes, its linked controls are one click away—so impact review starts from the relationship, not a search.
Procurement's vendor register links to third-party risk assessments in the GRC Solution. Both teams keep their own workflows while working from one vendor Record—no duplicate vendor lists drifting apart.
Findings raised in an audit Solution link back to the audited controls and forward to remediation projects—so every finding carries its origin and its fix, across Solutions, for the full lifecycle.
Pair Cross-Solution Linkage with Lookup & Rollup Fields to aggregate open findings, overdue tests, and residual risk from linked Solutions into one program-level register.
Features that work alongside this one.
Yes. Linked Record Fields connect Tables within and across Solutions, so Records in one Solution can reference Records in another—with the link mirrored on both sides automatically.
Yes. Once Records are linked, Lookup Fields display values from the linked Solution, Rollups aggregate across the linked Records, and Formulas can compute on the results.
Yes. Linking two Records creates a mirrored association visible from both Records, whichever Solution each lives in.
Access follows permissions. Members can open linked Records only when they have permission to the linked Table or Solution, so cross-Solution connections never bypass access control.
Yes. A Linked Record Field can allow single or multiple links, restrict selection with static or dynamic filters, or be set to only allow new record creation—so builders decide exactly how connections form.
No. It's how SmartSuite's Linked Record Field works—connecting Tables within and across Solutions is built into the platform's relational data architecture, with no separate add-on to buy.
Connect Every Register Without Copying a Single Record
Link risks, controls, policies, and vendors across Solutions—and let one relational model answer the questions spreadsheets never could.