> 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.md).

# Sections

## Overview

The Sections category provides widgets for displaying sections from other records directly inside the current Labii ELN or LIMS record. These widgets help teams reuse SOPs, shared instructions, attachments, and other controlled reference content while keeping the source material connected to its original record. Whether you want to select the source record manually or derive it automatically from a relationship field, these tools reduce duplication and keep cross-record documentation more consistent. They are especially useful in template-driven, collaborative, and compliance-oriented workflows where the same reference content needs to appear in multiple operational records.

## Widgets

* [Section Display By Record](/widgets/section-widgets/data-display/sections/section-display-by-record.md) - Display sections from a manually selected source record
* [Section Display By ForeignKey](/widgets/section-widgets/data-display/sections/section-display-by-foreignkey.md) - Display sections from a relationship-linked source record


---

# 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:

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

The question should be specific, self-contained, and written in natural language.
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.