Properties

Properties give every Object of a Type consistent, queryable fields. Add them from Object type settings → Properties or while creating a Type.

Property kinds

Lar’s model supports text, rich text, number, checkbox, date, datetime, URL, color, select, multi-select, structured table, and JSON values. The property picker presents the user-facing subset appropriate to the current schema surface.

Select and multi-select properties can be free-form, or can define stable options with labels and colors. Number properties can display as a number, progress value, percent, currency, or cryptocurrency. Date properties can control whether time and date ranges are optional, required, or unavailable.

Add a property

1. Open the Type’s settings.
2. Select Properties.
3. Choose Add property and select a property kind.
4. Enter a unique name and any kind-specific options.
5. Open the new property to configure its description, icon, visibility, format, or AI auto-fill settings.

The effective schema includes inherited and mixed-in properties. A new own property cannot silently reuse one of those names.

Control where a property appears

Property visibility can be:

• Always show — keep the row visible even when empty.
• Hide when empty — show it after a value exists.
• Hidden — omit it from the default Object page while keeping it stored and queryable.

Type layout and card settings provide additional control over ordering and which fields appear in different presentations. Hidden technical properties on file-backed Objects can be surfaced through their specialized viewers.

Rename or change a property

Renaming retains the old name as an alias so existing references can continue to resolve.

Changing a property’s value type is an explicit conversion. Lar creates the replacement definition and coerces each Object’s value where possible; values that cannot be converted are not something to ignore. Review the conversion result before treating the migration as complete.

Removing a property is also a schema-level action affecting every Object of the Type. The schema follows append-only evolution rules: deprecated fields and aliases preserve meaning across changes rather than allowing silent reinterpretation.

Formula and read-only properties

A formula derives a value from other properties and is read-only in the Object editor. Some read-only properties are filled by imports, uploads, or Lar features.

Next: Inheritance.