Admingen uses tabs in three places. They solve different tasks and do not combine records into one save operation.
| Tabs | What they organize | Setting |
|---|---|---|
| Form tabs | Sections and fields of one persistent record | Add tab |
| Module entity tabs | Separate entity pages in one navigation group | Entity navigation → Tabs |
| Virtual related-content tabs | Selected read-only relationship groups | Related content → Tabs |
Split a long form
- In Admin editor, select a persistent entity.
- Click Add tab.
- Select the tab and set Properties → Title, for example
DetailsorPublishing. - Add sections and rows, then place fields in them. To move a placed field between tabs, use Move field to tab in Properties.
- Use the tab strip to check each part, then Save layout and Generate.
A field belongs to one place in the complete layout, not one place per tab. Tabs organize the same record: switching between them does not create independent records. In the generated form, validation can reveal the tab containing a field that needs attention.
Put a module's entities under tabs
Select an entity assigned to a module. In Properties, find that module and change Entity navigation from Group to Tabs. Save and generate.
For example, a Content module can show ENTITY_NAME, RELATED_ENTITY_NAME and TAG_ENTITY_NAME as entity tabs. Each entity keeps its own route, list, access rules and record-save operation. Changing navigation does not grant access to an entity that the user cannot read.
Show virtual relationships as tabs
Select a virtual entity, then change Related content → Blocks / Tabs. Blocks stack selected relationship groups vertically; Tabs lets the reader switch between groups. The projection's selected fields and collections still come from Content / Virtual entities.
This is a read-only presentation setting. It does not add editing of virtual records, writes to related entities or a transaction that saves several records together.
Appearance of generated tabs
Related-content tabs, their selected state and indicator follow the nearest Content surface after generation. Form tabs remain inside the form surface; read-only details can have headings and tabs on the page background. Readable foreground tones can differ across these areas when their backgrounds differ. Configure palettes through Branding; tab arrangement still belongs here.