Relations

A Relation connects an entry to other entries, including entries from different Collections. Where a Tag picks from a list of labels, a Relation points at real entries — each with its own page, properties, and history.

For example, a Project can link to an Area, a person and a document in one Relation property. Adding these links does not create fields in the other Collections.

Adding a Relation property

Open + Add a property in the Collection's settings or on an entry's page and choose Relation. The property appears immediately, accepting multiple entries from any Collection, and its settings open alongside it.

You can adjust:

• Name — for example, Area, Goal or Blocked by.
• Allowed collections — leave unrestricted, or select one or several Collections. Your own Collection is allowed too.
• One or many — choose one target per entry or allow several.

You can close settings and start linking immediately. Adding more links keeps them in the same field; it never creates more properties.

Using it

A relation shows as chips followed by a + button. Click + to search the allowed Collections and pick entries; click a chip to jump to that entry's page. Click the × on a chip to remove that link — it goes at once, and the message that appears has an Undo button to put it back. Everything updates instantly.

It works the same everywhere you see the relation: on the entry's page, on a card, and in an opened list row.

Don't see the entry you want? Type its name and hit Create "…" — choose where to create it when more than one Collection is available. The new entry is created and linked together.

When there are a lot of them

A relation with many links doesn't take over the page. The field shows the first couple of lines of chips and puts the rest behind … N more — click it to open the full list, which grows to five lines and then scrolls on its own. Show less folds it back. The + button stays reachable the whole time, so you can keep linking without expanding first.

This holds at any size: hundreds or thousands of links stay fast, because only a slice is drawn at a time (with a Load more button for the next batch). In table cells, where there's no room to expand, you see the first few chips and a +N count — open the entry to see them all.

Choose whether to show the other side

The connection can be found from either end, but the other Collection gets no new field automatically. To display the reverse side, open Add a property → Add existing relationship there and choose the relationship.

For example, Projects can have an Area field while Areas shows no Projects field. Add that existing relationship to Areas when you want a list of linked projects. Name it Projects, hide it or remove its display without changing the links.

Each side has its own name, visibility and position. Open the property's settings from either displayed side to adjust the shared relationship rules. You never need to navigate to the Collection where it was first created.

Removing a linked chip removes that connection from both ends, without deleting either entry. Removing the reverse property display leaves the links intact.

For one combined overview, add Related Entries through Add a property. It shows direct Relations, body links and parent/child connections together, with the reason for each connection. It stays available even when individual reverse fields are not added.

To restrict an existing Relation, edit Allowed collections. If existing links fall outside your selection, change those links first; changing the setting does not silently delete them.

Relations and the AI

Relations are built for asking, not just clicking. The assistant can create relation properties, connect entries by name ("put the Marathon project under my Health area"), and read the graph in both directions ("what's in my Health area?"). If a name is ambiguous it asks rather than guessing.

Relation, Sub-entry, or link?

• Relation — points at an independent entry that lives its own life. Deleting a project never touches its area.
• Sub-entries — the children are part of the entry (a dish's ingredients) and are deleted with it.
• @-link in the text — a lightweight mention inside a page's body; no structure, no one-or-many, just a reference and a backlink.

Rule of thumb: if the thing you're connecting to deserves its own page and would outlive this entry, it's a Relation.

Next

• Properties and permanent fields
• Sub-entries