> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/widgets/section-widgets/data-display/sections/section-display-by-record.md).

# Section Display By Record

## Specs

| Label                     | Value                                  |
| ------------------------- | -------------------------------------- |
| **Version**               | Not documented (updated on 2026-06-14) |
| **Developer**             | Labii Inc.                             |
| **Type**                  | Section                                |
| **Support Configuration** | Yes                                    |

## Overview

The Section Display By Record widget displays one or more sections from another Labii record inside the current record, allowing teams to reuse content without copying it manually. Unlike the ForeignKey-based variant, this widget lets users explicitly select the source record in the widget configuration. It is useful for showing SOP procedures, shared instructions, common attachments, or reference sections from master records while keeping related content visible where work is actually being documented. This approach improves consistency, reduces duplication, and supports controlled reuse across experiments, projects, and regulated workflows.

## Use Cases

* **SOP Reuse**: Display procedure sections from an SOP record inside an experiment record.
* **Shared Reference Content**: Surface common instructions, files, or notes from a master record in downstream work records.
* **Template Support**: Reuse standard sections across records without duplicating the original source content.
* **Cross-Record Review**: Bring reference sections into the current record so collaborators can review them in context.
* **Compliance Workflows**: Freeze displayed content to a selected source version for traceable review and approval.

## Interface

### Read-only View

In read-only mode, the widget displays the selected source sections directly inside the current record without allowing in-place edits. This mode is used when **Is Readonly** is enabled or when a specific **Version** is selected.

* **Data Display**: Shows sections pulled from the selected source record inside the current record layout.
* **Source Awareness**: Uses the manually selected source record as the content origin.
* **Version Awareness**: Can follow the newest source content or display a fixed version.
* **Review Use**: Useful for controlled references, SOP review, and signed-record workflows.

<figure><img src="/files/ABqEGCw2z6l3cKNlMCi3" alt="Read-only view of the Section Display By Record widget"><figcaption><p>The read-only view displays sections from the selected source record inside the current record.</p></figcaption></figure>

### Edit View

In edit mode, users configure the source record and decide whether the displayed sections should remain editable or frozen. If **Is Readonly** is cleared and no fixed version is selected, the source sections can be displayed in an editable form.

* **Input Methods**: Search for and select the source record to display.
* **Formatting Options**: Choose whether to follow the latest source content or pin the display to a specific version.
* **Validation**: The source record must exist and contain the sections you want to surface.
* **Collaboration**: Supports deliberate reuse of source content while controlling whether users can edit the displayed result.

<figure><img src="/files/YWMoFdiaZCiI8unhVlZ7" alt="Edit view of the Section Display By Record widget"><figcaption><p>The edit view lets users select the source record and control versioning and read-only behavior for displayed sections.</p></figcaption></figure>

{% hint style="info" %}
This widget differs from Section Display By ForeignKey because the source record is selected directly in the widget configuration rather than derived automatically from a relationship field.
{% endhint %}

## Configuration

### Initial Setup

{% stepper %}
{% step %}
Open the record and add the **Section Display By Record** widget to a section.
{% endstep %}

{% step %}
Switch the section to **Edit** mode or open the widget settings.
{% endstep %}

{% step %}
Search for and select the **Target Record** that contains the sections you want to display.
{% endstep %}

{% step %}
Optionally select a source **Version** or enable **Is Readonly**, then save the record.
{% endstep %}
{% endstepper %}

### Required Settings

* **Target Record**: Select the source record whose sections should be displayed inside the current record.

### Optional Settings

* **Version**: Select a specific version of the source record when you need the displayed content to remain fixed instead of following the latest source updates.
* **Is Readonly**: Display the source sections in read-only mode when the content should be reviewed but not edited from the destination record.

{% hint style="info" %}
If no version is selected, the widget uses the newest version of the source record. When the current record is signed, a latest version is assigned automatically.
{% endhint %}

### Advanced Configuration

For scalable reuse, maintain dedicated source records for procedures, standard content blocks, or shared reference sections.

{% stepper %}
{% step %}
Create source records that contain reusable sections such as SOPs, standard attachments, or reference notes.
{% endstep %}

{% step %}
Use version pinning when approvals, signatures, or audits require a stable reference to a specific source state.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
If the wrong source record is selected, the widget may display valid content that is contextually incorrect. Always verify the target record before relying on the displayed sections in regulated or template-driven workflows.
{% endhint %}

## Additional Functions

### Manual Source Selection

This widget gives users direct control over which source record provides the displayed sections.

* **Explicit Source Control**: Lets users choose the exact record to reference.
* **Flexible Reuse**: Supports cases where the source record is not already stored in a relationship field.
* **Reduced Duplication**: Reuses source content without copying sections into each destination record.

### Version Pinning

Use version selection when the displayed source content must remain stable for review or compliance.

{% stepper %}
{% step %}
Open the widget configuration.
{% endstep %}

{% step %}
Select the source **Version** you want to display.
{% endstep %}

{% step %}
Save the record and confirm that the intended source version is shown.
{% endstep %}
{% endstepper %}

### Integration Features

* **Record Reuse Integration**: Works well with SOP libraries, master template records, and other controlled source content.
* **Documentation Integration**: Keeps referenced sections visible alongside the current record's own sections and data.
* **Workflow Integration**: Supports review workflows where the source record must be chosen deliberately per record.

### Version Control and Audit Trail

* **Version Traceability**: Supports fixed source versions for controlled documentation and approval workflows.
* **Configuration Traceability**: The selected target record remains part of the widget configuration.
* **Record Integrity**: Encourages a single authoritative source for shared sections while still making the content available where needed.

## Best Practices

### Data Organization

* Maintain clearly named source records for reusable procedures, templates, and shared reference content.
* Use this widget instead of copying and pasting common sections into multiple records.
* Keep source records curated so destination records surface clean, trustworthy content.

### Workflow Design

* Use **Version** pinning when downstream records must preserve the exact source content used during review or execution.
* Leave the widget unpinned only when users should always see the newest source version.
* Prefer this widget over the ForeignKey-based variant when source selection should vary case by case.

### Review and Compliance

* Verify the selected source record before signing or approving records that depend on displayed sections.
* Use read-only mode for controlled references that should not be changed from the destination record.
* Record why a given source record was selected when the destination record depends on a specific reference source.

{% hint style="success" %}
This widget works best when source records are maintained as authoritative references and destination records use them to surface context-specific guidance without duplicating content.
{% endhint %}

### Common Pitfalls to Avoid

* **Avoid selecting a source record casually**, because the widget will faithfully display whatever record you choose, even if it is the wrong one for the workflow.
* **Avoid assuming content is frozen when no version is selected**, because the widget follows the newest source version by default.
* **Avoid mixing reusable source content with ad hoc notes**, because destination records should pull from a controlled, understandable source.

## Related Widgets

* [Section Display by ForeignKey](/widgets/section-widgets/data-display/sections/section-display-by-foreignkey.md): Use this widget when the source record should be derived automatically from a relationship field instead of being selected manually.
* [ForeignKey](/widgets/column-widgets/form/dropdown/foreignkey.md): Use this column widget when you want the source record relationship stored as structured data for the ForeignKey-based section display workflow.
* [ForeignKeys](/widgets/column-widgets/form/dropdown/foreignkeys.md): Use this column widget when multiple related records need to be stored for workflows based on automatic relationship-driven source selection.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.labii.com/widgets/section-widgets/data-display/sections/section-display-by-record.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.