In the generated admin you work with data: create articles, update products and upload images. Saving a form writes data to PostgreSQL. It does not change the project structure, which is managed in Generator UI.
Sign-in and navigation
You need an account; the operator creates the first one using bootstrap instructions. After signing in, open the required module and entity in the menu. Hiding a menu item does not itself protect data: the server also checks access on every request.
Persistent entities can have List, Details, Create, Edit and Delete, depending on generated capabilities and your permissions. Projections support reading only. Modules organize navigation but do not grant access to every entity inside.
Record list
The list displays the current page's records, total count and page navigation. Data takes most of the table; actions are on the right. Related records opens associated records; Delete removes a record after confirmation. Hover over a cell to see whether its contents can be opened.
Search, filter and sort through available list controls. These capabilities are enabled per field in Generator UI under List behavior. String/text search, type-specific filters and sorting run on the server before pagination. Virtual settings are independent of the source entity, and collections in a record card have their own controls. If a capability is missing, check the field in the generator and update the application after Generate.
Creating and editing
Fill the form and save. If a value fails validation, correct it and retry. A network error does not confirm that the record was saved. If the result is uncertain, reload the record first: the server may already have accepted the change.
Hidden/Readonly behavior, required fields and formats are described in field rules. For a custom editor, note that FormData saves the complete current object rather than arbitrary PATCH merging. Preserve fields the editor does not yet display. Otherwise, an old client may lose a newly added manifest field's value.
Relationships and images
Start typing the related record's name: options load asynchronously with a bounded result count. Related records opens available inverse collections. Change many-to-many membership on the relationship owner with the required permissions; the inverse view displays membership only.
In Image/Gallery, wait for file uploads to finish before saving the record. Fix or remove failed items first. Image upload and form save are separate actions; see images.
Adapting the interface
Select Presentation → Markdown in Generator UI for a visual article editor with source mode. Multiline, JSON, dates, enums and media also have built-in inputs. Implement special behavior in custom UI while preserving form rules. You may replace an entire page, but then its maintenance belongs entirely to the developer. See extensions.
Optional: CLI
The generator CLI edits the application model; use the admin for everyday record changes. Startup, migrations and maintenance are covered in operator commands.
Keep the two interfaces separate
Change fields and access in Generator UI, then Generate. Record changes take effect after form save and require no regeneration.