Create and edit an Object Type

Create a custom Object Type when a category of information needs a consistent schema or presentation.

Create a Type

1. Open New and choose the option to create a new Object Type.
2. In Identity & inheritance, enter a name, choose an icon and color, and select a parent Type. Every Type ultimately descends from Note.
3. In Mixins, attach any reusable property bundles the Type should carry.
4. In Properties, add the fields that belong specifically to this Type. The preview shows own, inherited, and mixed-in fields together.
5. Resolve any name conflicts shown by the wizard, then select Create.

The creation wizard does not write a partial Type at every step. It keeps a draft and creates the definition after its schema is valid.

Open Type settings

Use the menu beside a Type in the sidebar and select Object type settings. The available sections depend on whether the Type is built in or custom.

For a custom Type, settings can include:

• General — name, singular/plural labels, icon, color, description, and whether the Type has a body.
• Inheritance — view or change the single parent and inspect the inheritance chain.
• Properties and Relations — edit the schema.
• Mixins — attach or remove reusable bundles.
• Calendar settings — shown when the Type has a date or datetime property.
• Default link view — choose how links to Objects of this Type open.
• Templates — create, edit, import, export, and choose a default.
• Customize layout, Page layout, and Card view — choose fields and sections shown on pages and cards.
• Automations — open workflows scoped to the Type.

Built-in Types expose only settings that are safe to customize. Their application-owned schema cannot be freely rewritten.

Design a useful Type

Start with the minimum structure shared by every Object of the Type. Prefer:

• inheritance for a true is-a relationship;
• a Mixin for structure shared across unrelated Types;
• a relation for a connection to another Object; and
• a template for suggested starting content rather than a schema requirement.

Avoid adding a property only because one Object needs it. You can add it later if the pattern repeats.

Delete a Type

The Delete section is intentionally separate from ordinary settings. Read the confirmation carefully: deleting a Type definition and handling Objects that use it are broader operations than deleting one Object. Export or convert important Objects before removing a Type.

Next: Properties.