Browse topics

Properties and the Title

11 min read

Properties are what a Collection tracks — every Entry of the Collection carries one value per Property. From a plain number to a live stopwatch to coloured tags to a full block editor Page. Every Collection also has a built-in Title — the headline on each Entry's card.

A Collection is the shape of something you track. The Properties are the pieces of data inside that shape — every Entry of the Collection carries one value for each Property. Every Collection also has a built-in Title — the headline on each Entry's card in the feed, which defaults to the Collection's name but is yours to change per Entry.

This page covers how Properties work and how the Title works. For the list of every type, see Every property type.

Adding a property

Choose Add a property. General types appear under Basic, followed by Time, Entry information, Relationships, Calculations & controls, and Special tracking. Date & time handles dates with optional times; Scale values multiplies other number fields. The small grey hint shows the data type, with read-only first when you cannot edit the value.

Named shortcuts such as Protein or Weight are no longer offered as separate types. Existing fields and their values keep working. Heart rate and GPS distance remain in Special tracking. Screen time breakdown and Source log appear when connected sources create them; to bring back a removed one, open that source in Settings and choose Restore removed properties.

Properties

Every Property has three things:

  • a name (reps, hours, note)
  • a type — the kind of data it holds (see Every property type)
  • an optional default value that fills in automatically when you quick-log

For a Color property, open the Collection's Properties tab and click the color swatch to set its default. The picker offers the same preset colors, custom hex input, and Clear color action as an Entry. On the mobile app, open the property's settings and tap its default color. This sets the starting color for new Entries; existing Entries keep their colors.

When you log an Entry on a Collection, you write one value per Property. Most Collections have 1–4 Properties. Anything beyond that usually wants to be split into multiple Collections, or composed with Sub-entries.

Permanent entry properties

Built-in properties use the same row spacing and aligned labels as your other properties, both on entries and in Collection Properties.

Five built-in properties are available through Add a property, alongside your custom properties. None is added to the Collection by default. Add each one once, then use its normal property settings to name it and control visibility.

PropertyWhat it shows
Entry dateThe editable date and time that place the entry in your log, chat timeline and calendar.
Created atWhen the entry was created. Read-only.
Updated atWhen the entry's content was last changed. Read-only.
Related EntriesDirect links to and from other entries, including Relations, body references and parent/child connections.
FilesFiles used by this entry, including files in its body, file/image properties and its banner.

Hide keeps the property in your configured list and controls whether it appears on entry pages. Choose Always show, Hide when empty or Always hide. Remove takes its display out of this Collection's property list. Neither action deletes dates, files or links, and the assistant can still read the information.

Adding the property again shows the same underlying information. Removing Entry date does not move entries out of the calendar or change their dates. Fields you explicitly display in cards or tables remain independent.

For example, you can create a diary entry today and set its Entry date to yesterday. It appears in yesterday's log while Created at still records today. Every entry has an Entry date: when none is supplied, it uses Created at. Resetting the date restores that creation time.

Files lets you open a file and see Used in links. A photo used in two entries has one file identity and two associations. Removing one use leaves the other intact. Related Entries explains why records are connected; edit the original Relation, body link or parent/child connection to change it.

Reading structured JSON data

A JSON property shows a short summary on entries, cards and tables. On an entry, choose View data to inspect its nested fields. For example, a timeline with two segments totalling 91 minutes reads 2 segments · 1h 31m.

JSON data is read-only by default. If its property configuration enables editable, choose Edit data to open the JSON editor. The assistant can also save an object or array into an existing JSON property without converting it to text. Provider-protected values remain locked in the entry editor.

Property icons

Every Property shows a small icon in the builder — by default the one for its kind (a # for Number, a tick box for Checkbox, and so on). Click that icon to change it: the picker opens with two tabs — Emoji and Icons (the full icon library, searchable by name). Pick a 🔥 or a flame icon for calories, a 🏃 for distance — whatever reads fastest for you.

A custom Property icon is remembered for this Collection only, so the same shared Property can wear a different icon in another Collection. To put it back, open the picker and choose Remove.

Every property type

Every type — what it holds, what it looks like, and when to use it — has its own page with pictures: Every property type.

Pick the type that fits how you want to read the data later. A number you want to add up or chart is a Number. A yes/no habit is a Checkbox. A label you want to group a board by is Tags.

Some Properties are filled in by a connected wearable, like Sleep's Bedtime and Wake time. A small ⟳ icon next to a property's name marks it as filled in by a connected source — hover or tap it to see where the value comes from. Most synced values can still be edited, and your edit sticks on the next sync. See Connecting Fitbit or Google Health.

The Title

Every Entry has a Title — the headline you read on its card in the feed. It's built in: every Collection has one automatically, so you never add it as a Property.

By default, an Entry's title is the Collection's name. Make a "Todoo" Collection and every todo you log starts out titled "Todoo". But the title is yours to change — type "Buy milk" on one, "Call the dentist" on another. Entries you never rename keep showing the Collection name, so renaming the Collection re-labels them all.

Two different things live in two different places:

  • The Collection's name — edited at the very top of the Collection builder. It's the Collection's identity and is the same for every Entry.
  • The default Entry title — the Title row at the top of the Properties tab. Leave it showing the Collection name to inherit it, or type a different default that every new Entry starts with. (Editing this does not rename the Collection.)
  • The Title's icon — the icon on that same Title row. It matches the Collection's icon by default, but click it to pick a different emoji or icon just for the title; choose Remove to go back to matching the Collection. Changing it here does not change the Collection's icon.

To rename one Entry, just edit its title right on the card — or open the Entry and edit the heading on its page. Because the card title is now an editable field, you open an Entry by clicking its card body or the ⋯ menu's Open.

Your other Properties — reps, hours, calories, a checkbox — show on the card next to the Title, each with its current value.

Defaults make logging fast

Defaults are the secret behind one-tap logging. If your Collection's Properties have sensible default values, tapping that Collection in chat writes a new Entry instantly with no extra input.

Set defaults thoughtfully:

  • Pick the value you log most often, not the average.
  • For habit tallies (vitamins, meds, water glass), true or 1 is almost always right.
  • For workouts that vary, leave the default empty and type the number — fast either way.
  • For Stopwatch/Timer, the default is "0m, ready to start" — the entry writes the moment you pick the Collection, then you Start the live counter on the card.

Adding, reordering, and deleting properties from an entry

You don't have to be in the Collection builder to change its schema. Open any Entry and hover a property row for its ⠿ grip: drag to reorder (the order is shared by the whole Collection), or click it for Rename, Visibility on this page, a shortcut to the card layout, and Delete from collection…. A + Add a property button under the list adds a new one — on the entry's own page, in the side panel a board opens, and on your phone. Adding and removing are immediate everywhere: the real row appears (or goes) the moment you act, even if you're mid-sentence in another field, and the save catches up behind you. See Editing an entry for the full rundown, including how hidden properties collapse and why hiding one on the entry page never touches the card or a view.

Changing a Property's kind

Picked the wrong kind, or your tracking outgrew it? You can change a Property's type after the fact — like turning a Number into Text. Open the Change type… action from any of three places:

  • the Collection builder — a property row's ⠿ menu → Adjust settings → Change type…
  • an Entry — a property row's ⋯ menu → Change type…
  • the table view — a column header menu → Change type

Pick the new kind and Kaizendex shows exactly what will happen to your existing values before you confirm:

  • Kept as-is — Text ↔ URL ↔ Email ↔ Phone ↔ Page all hold text, so nothing changes.
  • Kept as a number — Number ↔ Rating keeps every value. A number outside the new rating scale stays as it is and gets a small warning mark until you change it or widen the scale.
  • Converted — a Number becomes its digits as Text, a Tag becomes its label as Text, a Date gains or drops a time.
  • Cleared — values that can't be represented in the new kind are removed. Converting Text → Number drops any cell that isn't a number. The dialog tells you how many values this affects, and this part can't be undone — so read the warning before confirming.

Not every kind can convert: structural and computed kinds (Sub-entries, Relation, Formula, Rollup, Stopwatch, Timer, the wearable read-only kinds) don't take part, tag kinds aren't offered as Change type targets (use the settings switches instead), and turning plain text into Tags is coming later.

Edit a property's settings as JSON

Every switch in the property settings panel — a Formula's expression, a date's calendar role, a Stopwatch's auto-start, a Files & media property's size — is stored in one small settings document per property, and you can edit it directly: open Adjust settings and pick Advanced — edit property config JSON at the bottom. It's the same escape hatch charts and card layouts have: Apply checks the known settings and tells you exactly what's wrong and where before anything is saved. Most people never need it — it exists so power users and the AI can read and write the same settings the panel shows.

The Relation kind lets one Entry reference another Collection's Entry. Examples:

  • A Pages read Collection with a book Relation points each reading session at a specific Book.
  • A Set Collection with a workout Relation groups multiple sets under one workout session.
  • A Task done Collection with a project Relation organises completions under projects.
  • A Meal Collection with a recipe Relation points to a Recipe Entry with the ingredients.

Relations are how you build graphs across your tracking data without leaving the universal engine.

Next

Didn’t find your answer?Email me