Brand and custom data models
Adapt AIOS to the language, structure and identity of your business.
How it fits together.
Customization has several layers: Design changes appearance, Navigation changes menus, and Data model describes custom object types. The expanded editor displays forms alongside a preview. Domain settings follow a separate workflow. First decide whether you want to change the workspace or the structure of its information.
The model form starts with scope, names and fields, followed by capabilities and further settings. The resulting model has Overview, Design and Objects views. Design lets you inspect display, form and card presentations separately, helping you plan both data entry and how an item will be read later.
Step by step in AIOS
Open Settings → Organization → Customization.
Customization separates appearance and data structure. Open expands the editor so the form and preview can appear side by side.
Choose Design for appearance, Navigation for menus or Data model for custom object types. Visible sections depend on your permissions.
Choose the appropriate section before making a change. Menu changes belong in Navigation; a new object type belongs in Data model. Domains use their own configuration workflow.
Define the scope, name, fields and capabilities of a custom model.
Begin with the model’s purpose. Enter singular and plural names and add a few clearly described fields. Then decide which available capabilities the workflow requires.
Check the display, form and card previews in the model’s Design section. Save your form changes.
Display, Form and Card answer different questions: How do I read the item? How do I enter it? How do I recognize it in a collection? Check all three using a fictional item.
AIOSAn example for your work.
{
"summary": "Pilot completed",
"next_step": "Arrange the customer kickoff meeting",
"handover_date": "2026-10-01"
}This JSON illustrates data for the fields described above. Create the model and its fields in AIOS; this is not an importable model or API schema.
Shape models and the interface
| Area | Meaning in daily work |
|---|---|
| Organization design | Workspace appearance and preview. |
| Navigation | Menus according to navigation configuration permission. |
| Data model | Custom object types with names, fields and capabilities. |
| Model design | Display, form and card for the custom object type. |
| Model objects | Actual items of the configured type. |
If something does not work.
- Navigation or Domains is missing: Both have their own organization permission requirements.
- The card is difficult to scan: Check the model’s separate Card preview using a completed sample object.
- The field example cannot be imported: It is a planning aid. Create fields in the editor using its available types.