Folders and note properties

V2 identifies an entity through its type property. Its folder does not define whether it is a project, goal, or meeting. You can organize those notes by your own filing method.

Give notes a supported type

The recognized types are project, area, resource, goal, meeting, person, and note.

For example, a project note starts with:

---
type: project
status: ongoing
deadline: 2026-09-30
goals: []
---

An explicit unsupported type does not become a supported entity. Ordinary Markdown without a type resolves as a plain note outside the reviews and templates folders.

Creation commands ask for a destination folder. V2 does not use the old V1 folder-mapping settings to identify entities.

Use your own metadata

Project and goal statuses are free-form. Choose the labels that describe your work. Status does not itself determine completion.

The native pages view can filter custom properties:

view: pages
type: project
where: status=ongoing, priority=high
completed: false
sort: deadline

where uses property=value pairs and checks list values individually. Set archived: true on a note to archive it. Standard page views hide archived notes unless requested.

Use the icon property or Change file icon command for native file icons.

Preserve reserved locations

Keep creation templates under templates/obsibrain/. Keep periodic reviews under reviews/1-daily through reviews/5-yearly. Their paths and date formats identify review context.

The root dashboard is Dashboard.md. If you move or rename it, Open Dashboard treats the root dashboard as missing and creates a default there.

For a V1 vault, use the migration wizard before manual reorganization. Folder names and old tags alone do not establish all V2 identities.