Table Reports on the Record Page: A Modern Way to Display Linked Data

An Evolving Set of Features — First Available Now, More Throughout 2026

This article is your central resource for the Table Report-powered features replacing Layouts on the record page. We'll keep it updated as each new capability rolls out — bookmark it to stay in the loop.

Why We Recommend Table Reports on the Record Page

For years, Layouts have been the primary way to display linked record data on a record page. They work — but as our customers' GRC programs have scaled, the limits of Layouts have become clear. Builders want more control over what end users see. End users want to filter, sort, and search the data they're working with. Everyone wants a consistent, performant experience..

We heard a few themes consistently from customers:

• "My end users can't find the right records." Layouts don't support filtering, so users scroll through long lists looking for the right thing to link or review. Additionally, while layouts do support search, their search tool searches all fields/values on a record, returning too many results, and overwhelming end users. 
• "I don’t want to manage two versions of the same report." Builders had to configure Layouts and Table Reports separately, even when displaying the same underlying data.
• "I need to give my users more context without sending them somewhere else." Layout-powered relationship reports can't be filtered to a specific scope, and surfacing too much context, further confusing end users.

Table Reports on the record page solve all three. Instead of maintaining a parallel Layout configuration, builders can leverage their existing Table Reports — with their filters, sorting, columns, and settings — directly on the record page. End users get a familiar, powerful interface for finding and acting on linked data.

A note on Layouts: Layouts are not being retired. Any Layout you have configured today will continue to work, and you can continue to use them for as long as you'd like. However, new features on the record page (including everything described below) are being built exclusively on the Table Report infrastructure. To take advantage of these improvements, you'll want to transition your linked sections to Table Report mode over time.

Quick Guide: When to Use What

Each of the four features below solves a different problem. Use this table to decide which one fits your use case.

The most important distinction is between Table Report Record Linking (built for the linking workflow) and Embed Table Reports (built for viewing data). Read on for more on how to choose between them. 

Table Report Record Linking

Available Now

Table Report Record Linking lets you power a Linked Workflow Section with a Table Report instead of a Layout. End users get a robust, filterable, searchable interface for browsing and linking records — and builders can reuse the same Table Reports they've already configured elsewhere.

When to Use It

Use Table Report Record Linking when the act of linking records is the primary use case for the section. End users need to browse a list of candidate records, find the right ones, and link them to the parent record.

What You Get

• Pre-defined filters and sorting from the Table Report
• End-user filter and search to quickly find the right records
• Multi-select linking with checkboxes
• In-line editing of linked records (with proper permissions)
• Summary Fields default that auto-generates a Table Report from your workflow's Summary Fields — no manual setup required

Important Behaviors

Because Table Report Record Linking is optimized for the linking experience, a few guardrails are in place to keep things intuitive for end users:

• Force-flattened rows. Multi-workflow Table Reports are automatically flattened to prevent duplicate rows from confusing end users when they select records to link.
• Builder filters only apply to the Browse tab. On the "View Linked Records" tab, end users see all linked records regardless of any filters configured on the underlying Table Report. This ensures users can always see and complete required linked records, even if those records would normally be filtered out.
• Directly mapped workflows only. Records must come from a workflow that is directly mapped to the workflow containing the step.

These constraints are intentional — they prevent end-user confusion in the linking flow. If you need full Table Report flexibility (custom filters that persist, no forced flattening, multi-workflow data), use Embed Table Reports instead.

For configuration instructions, see: Add a Linked Workflow Section to a Step Form

Embed Table Reports

Coming Summer 2026

Embed Table Reports introduces a new section type that places a Table Report directly on the record page — automatically scoped to the current record's linked data. This is a view-only experience designed for displaying information, not for managing record relationships. Think of this as an 

When to Use It

Use Embed Table Reports when you need to display data from directly or indirectly linked records with maximum builder flexibility — and end users don't need to link or unlink records from this section.

What You Get

• Full Table Report flexibility. All Table Report settings are respected: filters, sorting, columns, and flatten behavior. Filters apply to everything the end user sees, not just a browse tab.
• Automatically scoped to the current record. The Table Report shows only the data relevant to the record you're viewing — not all records in the system.
• Multi-workflow data. Use Table Reports that span multiple workflows for richer context.
• Builder-controlled flattening. If you want to flatten duplicate rows, toggle the setting in the Table Report. If you want to preserve them, leave it off. Your choice.

Why Embed Table Reports Instead of Relationship Reports?

Going forward, we recommend Embed Table Reports as the standard way to display linked record data on a record page. Compared to Relationship Reports, Embed Table Reports offer:

• More predictable behavior with complex (many-to-many, circular) relationships
• Reusable Table Report configurations instead of one-off Relationship Report setups
• Builder and End-user filtering and sorting
• Improved query performance
• Out of the box support for all existing (and future) Table Report Settings

Existing Relationship Reports will continue to function. New configurations should use Embed Table Reports.

A note on permissions: Embed Table Reports respect the same record-level permissions as Table Reports elsewhere — users only see linked records they already have access to. No new permissions or sharing rules are introduced.

Bulk Create and Link with Table Reports

Coming Fall 2026

Bulk Create and Link (BCAL) lets end users create multiple child records at once from a list of source records. Today, that source list is powered by a Layout. With this update, builders can configure BCAL to use a Table Report instead.

When to Use It

Use Table Report-powered BCAL when end users need to bulk-create and link multiple child records from a source list, and you want them to be able to filter, sort, and search that source list to find the right records quickly.

What You Get

• Pre-defined filters and sorting carried over from the Table Report
• End-user filtering to refine the source list at link time
• Multi-select with full search instead of scrolling through long source lists
• A consistent BCAL experience that matches the rest of your Table Report-powered linked workflow surfaces

Bulk Create and Link will continue to work with Layouts. Switching to Table Report mode is a builder choice — make it when you want the filtering and search benefits.

Record Linking Recommendations with Table Reports

Coming Fall 2026

Spark AI Record Linking Recommendations uses generative AI to automatically identify and link data across key GRC elements within your Risk Cloud environment — saving end users from manually hunting for the right controls, risks, policies, or other related records.

Today, Record Linking Recommendations is only supported for Linked Workflow Sections configured with Layouts. With this update, it will also work on Table Report-powered Linked Workflow Sections.

When to Use It

Use this when you've enabled Spark AI in your environment and want AI-powered record suggestions to appear on Linked Workflow Sections that are using Table Report Record Linking.

What You Get

The same Spark AI Record Linking Recommendations experience your team may already be familiar with — Generate Recommendations, review Match Strength scores, link relevant records in a click — but now available on Table Report-powered Linked Workflow Sections.

For more on the current Record Linking Recommendations as a feature, see: Spark AI: Record Linking Recommendations

Frequently Asked Questions

Are Layouts being retired?

No — Layouts are not being retired in the immediate future. You can continue to use Layouts as long as you'd like, and any existing configuration will continue to work. That said, new features on the record page are being built exclusively on the Table Report framework, so transitioning to Table Reports over time will let you take advantage of new capabilities.

Will my existing Layouts continue to work?

Yes. There is no required migration, no deprecation timeline, and no impact to your existing configurations. Layouts will continue to function exactly as they do today. However, there is no plan to build any additional features/functionality for layouts

Can I use Embed Table Reports instead of Relationship Reports today?

Soon! The Embed Table Report feature is releasing in Summer 2026. Once it's available, we recommend using it as the standard way to display linked record data on a record page going forward. Existing Relationship Reports will continue to work.

How is Embed Table Reports different from Table Report Record Linking?

They solve different problems. 

• Table Report Record Linking is for letting end users link, browse, and manage relationships between records — and it includes guardrails (forced flattening, filter behavior on the Linked tab) to keep the linking flow intuitive. 
• Embed Table Reports is for displaying data only - not linking - but it gives builders the full flexibility of Table Reports without the linking-specific guardrails. 

If end users need to link records, use Record Linking. If they only need to view data, use Embed Table Reports.

Will Bulk Create and Link still work with Layouts?

Yes. Bulk Create and Link works with Layouts today and will continue to do so after the Table Report-powered version ships in Summer 2026. Switching to Table Report mode is optional and is a builder choice — make it when you want the filtering and search benefits.

Do Table Reports on the record page respect user permissions?

Yes. All Table Report-powered features on the record page — Record Linking, Embed Table Reports, Bulk Create and Link, and Record Linking Recommendations — respect the same record-level permissions, user group access, and workflow permissions that apply elsewhere in Risk Cloud. Users only see and can act on records they already have permission to access.

Last updated: June 2026 | This article will be updated as each new Table Report-powered feature is released.

We'll keep this article current as each capability ships. If you'd like to share feedback or have questions about how these features fit your program, reach out to your Customer Success Manager or contact us at support@logicgate.com.