Overview
Properties are the fixed, built-in fields that CXF defines for an object. They make up its base structure — the minimum set of fields the object needs to exist. Unlike Attributes, which you create and customize, Properties are defined by CXF and can’t be added, renamed, or removed. You extend an object’s base Properties with custom Attributes. Their values live side by side on the record; the UI usually presents them as separate groups. For the mental model, see Core concepts.Properties vs Attributes
| Properties | Attributes | |
|---|---|---|
| Defined by | CXF (fixed) | You (custom) |
| Purpose | Base structure — the minimum to exist | Extend the object with custom fields |
| Configurable | No | Yes |
Common properties
The exact Properties depend on the object type, but most objects share a base set, for example:| Property | Description |
|---|---|
id | Unique identifier of the record. |
title | Human-readable name. |
slug | URL-friendly identifier, unique within the object type. |
type | The record’s subtype within its object type, where applicable. |
created_at | When the record was created. |
updated_at | When the record was last changed. |
Behaviour & rules
- Properties are fixed — you can’t create, rename, or delete them; they’re part of the object’s definition.
- Property and Attribute values are stored at the same level on the record.
- Property values are set when you create or update a record.
Seeds
Because Properties are an object’s base fields, they appear directly inside a record’sdata in a structural seed — for example,
the title, slug, and type of a content template. See
Building a structural seed.
API access
Property values are read and written like any other field on the object through the API reference.Related
Attributes
The custom fields you add on top of Properties.
Object types
Each object type has its own base Properties.