Admin editor · 0.8.1

Admin editor: arrange the generated interface

Build readable forms from existing Content fields, then generate the updated admin.

On this page

Admin editor controls how the generated admin presents your model. Use it to place related fields together, split a long form into tabs, or organize related content. It does not create database fields or change access rules.

Open the editor

  1. Create an entity and its fields in Content.
  2. Open Account and check that Visual editor access is available.
  3. Open Admin editor in the generator menu.
  4. Select the entity in Entity. A Persistent or Virtual · Read-only badge identifies what you can arrange.

You can inspect a saved layout without editor access. Changing and saving the layout requires that access. Your generated application and already saved layouts do not stop working when a subscription expires.

Know which setting to use

Task Where to do it
Add a field, change its type, configure a relationship or access Content
Change field widths, rows, sections and form tabs Admin editor
Display a virtual entity's related groups as blocks or tabs Admin editor → Related content
Group a module's entity pages under navigation tabs Admin editor → Properties → Entity navigation
Add custom behavior or your own field component Custom zones

Content fields is a structure list. The + beside an unused field adds a placement to the form; this list is not a drag palette. Move existing placements on the central canvas. Select an element to edit its Properties on the right. On a narrow screen, the Properties button opens that panel from the right.

After arranging a form, use Save layout, then open Generate and review the generated changes. Saving a layout alone does not rebuild the application, migrate its database or deploy a release.

Start with rows and field widths, then read about tabs and saving and custom code.

Unplaced fields and visibility

In Admin editor, unplaced fields remain visible under the canvas in Other fields, so you can place them again. In the generated form, Other fields (N) is a flat disclosure button at the bottom, collapsed by default. Removing a placement does not remove the field or its values.

Hidden hides a field from both list and form; Readonly keeps it readable during editing. There are no independent Show in table / Show in form switches. Moving a placement to Other fields organizes the form; it neither restricts access nor removes the field from the API.