Modules
A Module is a sub-container within an application, used to organize the artefacts you build - entities, views, field types, and so on. Modules are hierarchical: a module can contain other modules, nested to any depth, so a large application can be broken down logically (e.g. “Sales” → “Sales / Quotes” → “Sales / Orders”) instead of leaving everything in one flat list.
Assigning things to a module
Section titled “Assigning things to a module”When you define an entity, view, field type, or other database artefact, you choose where it belongs: directly under the application, or under a specific module. This isn’t just cosmetic - it’s what makes module-based filtering and navigation work. For example, assigning a set of entities to an “HR” module lets you later filter the Entities screen down to everything that belongs to HR, and lets the generated application’s navigation group those entities together automatically.
Managing modules
Section titled “Managing modules”Modules are managed from the Application Modules list in the Edit Application panel (the gear icon next to the application picker).
A single + Add Module button creates a new module. If a module is already selected in the list when you click it, the new module’s Parent Module defaults to that selected module - making it quick to add a sub-module exactly where you’re working. Otherwise the new module is created at the top level, with the application itself as its parent.
Each module row has its own expand arrow (to reveal sub-modules), an edit (pencil) icon, and a delete (trash) icon.
Module settings
Section titled “Module settings”Clicking a module opens the Edit Module panel:
| Field | Description |
|---|---|
| Application Module Name | Human-readable name, e.g. “ERP” |
| Application Module ID | Auto-generated from the name, e.g. erp |
| Parent Module | Where this module sits in the tree - either the application itself (making it a top-level module) or another existing module (making it a sub-module). |
| Module Icon | An SVG icon for the module, used in navigation |
| Module Description | Rich text description of what the module covers |
Because Parent Module is just another field on the module, modules can be re-parented after creation - moving a module (and everything nested under it) elsewhere in the tree by editing this one field.