> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pregisteruitabsections.md).

# G2PRegisterUITabSections

g2p\_register\_ui\_tab\_sections - UI Tab Configuration (Sections) for Registers

Junction table associating G2PRegisterSection definitions with G2PRegisterUITab definitions. Defines **section ordering within a tab**.

Sections are defined once in `g2p_register_sections`; this table controls **where** each section appears and **in what order**.

***

### Attributes

| Attribute            | Description                                                   |
| -------------------- | ------------------------------------------------------------- |
| **tab\_section\_id** | Primary key. Uniquely identifies the tab–section association. |
| **register\_id**     | Register identifier (stored for query convenience).           |
| **tab\_id**          | References `g2p_register_ui_tabs.tab_id`.                     |
| **section\_id**      | References `g2p_register_sections.section_id`.                |
| **section\_order**   | Order within the tab. Lower values appear first.              |

***

### Relationship model

{% code lineNumbers="true" %}

```mermaid
erDiagram
    G2PRegisterUITab ||--o{ G2PRegisterUITabSection : "has"
    G2PRegisterSection ||--o{ G2PRegisterUITabSection : "included in"

    G2PRegisterUITab {
        uuid tab_id PK
        uuid register_id
        string tab_label
        int tab_order
    }

    G2PRegisterUITabSection {
        uuid tab_section_id PK
        uuid tab_id FK
        uuid section_id FK
        int section_order
    }

    G2PRegisterSection {
        uuid section_id PK
        uuid register_id
        uuid section_register_id
        string section_mnemonic
    }
```

{% endcode %}

A section definition may appear in multiple tabs via multiple junction rows.


---

# 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.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pregisteruitabsections.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.