Linked Records — Connect Your Work Into One Relational Graph
Link Records between Tables—within a Solution or across Solutions—with automatic two-way relationships, so shared data lives once and shows up everywhere it matters.
What Is Linked Records?
Linked Records is a SmartSuite field type that connects Records between Tables—within the same Solution or across different Solutions—so teams share data instead of re-entering it. Linking a Record in one Table automatically creates the reciprocal association in the other, giving every relationship two navigable sides. It is available on all SmartSuite plans and is the foundation for calculated relationship fields like Lookup & Rollup Fields.
Two-Way by Default
Link Records Once and See the Relationship on Both Sides
When you link a Record, SmartSuite automatically creates a mirrored Linked Record field in the target Table—Contacts show their Account, and the Account lists its Contacts, with no second field to maintain. Links work within a Solution or across Solutions in your Workspace.
One relationship, entered once, navigable from either side.
Configurable Selection
Control How Records Are Linked and Displayed
Choose the target Table, single or multiple selection, which fields display and in what order, and whether users can create new Records straight from the field or select existing ones only. Dynamic filtering narrows which Records can be chosen, and the selector supports grouping, sorting, defaults, and cover images from a Files and Images field.
Display formats—Compact, Simplified, Standard, Expanded, and Table—fit the relationship to the space it appears in, and linked values stay editable inline from Grid View.
Built to Build On
Power Lookups, Rollups, and Formulas Through Links
Linked Records are the rails other fields run on: Lookup fields display values from a linked Record, Rollup fields aggregate numbers across all linked Records, and Formulas reference linked data through chains up to three Tables deep—like SUM([Line Items].[Total]) on an order.
Relationships stop being lines on a diagram and start doing the reporting work.
Governed Relationships
Scale Connections With Permissions and Plan Headroom
Managing Linked Record fields requires Solution Manager or Administrator permissions, so the data model changes deliberately while everyone works within it. Per-Table field counts scale by plan—30 on Team, 50 on Professional, and 100 on Enterprise and Signature.
The relational graph grows with your organization without growing out of control.
Linked Records
Governed workflows are relational by nature—risks map to controls, findings to audits, vendors to assessments. Linked Records make those relationships part of the data.
Link each risk to the controls that mitigate it. Both sides stay navigable—open a control and see every risk it covers, open a risk and see its full control coverage.
Connect vendors to their assessments, contracts, and findings across Solutions, so third-party risk reviews start from one linked Record instead of four spreadsheets.
Link each finding to the audit that raised it and the control it tests. Recurring weaknesses surface on the control itself, and remediation planning starts from the real dependency picture.
Policy Records link to their attestation Records—open a policy and see exactly who has attested and what remains outstanding, from either side of the relationship.
Pair Linked Records with Lookup & Rollup Fields to surface totals and source values across relationships—open findings per vendor, total contract value per supplier.
Governed workflows are relational by nature—risks map to controls, findings to audits, vendors to assessments. Linked Records make those relationships part of the data.
It is a field type that connects Records between Tables—within the same Solution or across different Solutions—so teams share data instead of duplicating it. Linking from one side automatically creates the reciprocal association on the other.
Two-way by default. SmartSuite automatically creates a mirrored Linked Record field in the target Table, so the relationship is visible and navigable from both sides—there is no separate one-way link type.
Yes. Linked Record fields can target Tables in the same Solution or in other Solutions across your Workspace, which is how departments share customer, vendor, or asset data without copies.
Yes, if you allow it. Each field can permit creating new Records directly from the selector or restrict users to selecting existing ones, with dynamic filtering controlling which Records are eligible.
Field counts scale by plan: 30 Linked Record fields per Table on Team, 50 on Professional, and 100 on Enterprise and Signature—the same tier structure as other calculated fields.
Formula reference chains that traverse Linked Records are limited to a depth of three Tables (A to B to C). That is a constraint on formula chains, not a cap on linking itself.
Managing Linked Record fields requires Solution Manager or Administrator permissions. Everyone else uses the relationships—selecting, navigating, and editing linked values inline—without changing the data model.
Stop Copying Data Between Tools and Teams
Link your Tables into one relational graph—entered once, connected everywhere, governed throughout.