Have you read a contributing guide?
Clear and concise description of the problem
Allow the built-in Name property to be renamed on a per-Type basis, achieving parity with Notion's title property. The property would remain functionally special (object title, search index, link/mention display, graph node label) — only its display label would be customizable per Type.
A Contact Type is the clearest example. The natural schema is First name and Last name, but every object already carries the immutable Name property. This forces an awkward choice:
- Put the full name in Name and duplicate data into First name/Last name properties (manual, drifts out of sync), or
- Leave Name semantically meaningless for this Type and tolerate a confusing extra field in every object header and query view.
If Name could be relabeled to Full name (Contact), Title (Book), SKU (Inventory item), Part number (Component), etc., the built-in property would integrate cleanly into each Type's schema instead of colliding with it. Notion users migrating to Anytype hit this immediately, since renaming the title column is a standard step in any Notion database setup.
Suggested solution
In the Type editor (Space Settings → Content Model → Types, or the Type's property panel), allow editing the display label of the Name property, exactly as Notion allows renaming its title column. Constraints stay as-is: cannot be deleted, cannot change its format, exactly one per Type. The underlying property ID stays name, so queries, API, and sync are unaffected — this is purely a per-Type display label stored in the Type definition.
Alternative
-
Using Name as the full name and adding only a Last name property for sort purposes — workable, but the label "Name" remains generic and the schema reads poorly for Types where the title is conceptually something else (SKU, part number).
-
Formula/computed properties (Name = First name + Last name) would also solve the contact case, but that is a much larger feature; a rename is a small, self-contained win.
Additional context
Notion's title property demonstrates the model works: rename freely, but it cannot be deleted, retyped, or duplicated. Anytype already treats Name as special in exactly the same ways, so this is a display-layer change rather than a data-model change. Likely related to existing forum discussions on customizing system properties and on formula support.
Have you read a contributing guide?
Clear and concise description of the problem
Allow the built-in Name property to be renamed on a per-Type basis, achieving parity with Notion's title property. The property would remain functionally special (object title, search index, link/mention display, graph node label) — only its display label would be customizable per Type.
A Contact Type is the clearest example. The natural schema is First name and Last name, but every object already carries the immutable Name property. This forces an awkward choice:
If Name could be relabeled to Full name (Contact), Title (Book), SKU (Inventory item), Part number (Component), etc., the built-in property would integrate cleanly into each Type's schema instead of colliding with it. Notion users migrating to Anytype hit this immediately, since renaming the title column is a standard step in any Notion database setup.
Suggested solution
In the Type editor (Space Settings → Content Model → Types, or the Type's property panel), allow editing the display label of the Name property, exactly as Notion allows renaming its title column. Constraints stay as-is: cannot be deleted, cannot change its format, exactly one per Type. The underlying property ID stays name, so queries, API, and sync are unaffected — this is purely a per-Type display label stored in the Type definition.
Alternative
Using Name as the full name and adding only a Last name property for sort purposes — workable, but the label "Name" remains generic and the schema reads poorly for Types where the title is conceptually something else (SKU, part number).
Formula/computed properties (Name = First name + Last name) would also solve the contact case, but that is a much larger feature; a rename is a small, self-contained win.
Additional context
Notion's title property demonstrates the model works: rename freely, but it cannot be deleted, retyped, or duplicated. Anytype already treats Name as special in exactly the same ways, so this is a display-layer change rather than a data-model change. Likely related to existing forum discussions on customizing system properties and on formula support.