Entities & Fields — Backend Fundamentals

Entities are the records your backend stores. Fields are the values stored on those records.

Create entities and fields that are clear enough for Avora to generate database models, schemas, and useful API inputs.

Use singular entity names such as User, Order, Product, or TeacherProfile.
Add only fields that belong to the record itself.
Use relationships for links to other stored records instead of duplicating the other record's fields.
Choose the narrowest useful field type, including workspace enums when the value must come from a fixed set.
Add descriptions when a field name is not enough for AI, teammates, or generated docs.

Field decision	Use it when	Example
Normal field	The value belongs directly to this record	`Product.price`
Enum field	The value must be one of a fixed list	`User.role`
List field	One record stores several simple values	`Article.tags` as text list
Relationship	The value points to another stored record	`Order` connected to `Customer`
Profile entity	Role-specific user data should stay separate	`TeacherProfile`, `StudentProfile`

Each entity should describe one backend object cleanly, with fields that can become database columns and request fields without extra interpretation.

Use Diagram Builder for the full attribute workflow.