Skip to content

Objects

Everything in AuroraDocs is an object. A page, a task, a database, a bookmark, a canvas — they are all objects. This is the core idea that makes AuroraDocs different from most note-taking tools.

What is an object?

An object is the fundamental unit of content in AuroraDocs. Every object has:

  • A type (page, task, database, etc.)
  • A title
  • An optional icon and cover image
  • A body — rich content written in the editor
  • Properties — structured fields like status, date, assignee, or any custom field you define
  • A unique ID that can be referenced from anywhere

Because every object shares this structure, they compose naturally. A task can contain a full document. A database row is a page. A page can embed a database. You don't need to decide upfront what something "is" — you can refine it later.

Built-in object types

TypeWhat it's for
PageA document, note, or any long-form content
NoteA lightweight page for quick notes and Inbox capture
TaskAn actionable item with status, priority, and due date
DatabaseA structured collection of rows, each of which is also a page
SetA dynamic or static collection of other objects (see Sets & spaces)
CanvasAn infinite whiteboard for spatial, freeform thinking
BookmarkA saved URL with auto-fetched title, description, and preview image
FolderA hierarchy container for grouping pages and objects
Daily noteA journal entry automatically created for each calendar day

Optional built-in types such as People, Meetings, Trips, Projects, Images, Quotes, Links, and Backlog can be enabled per workspace. These can include starter fields, built-in templates, and default views such as gallery-first Images or Kanban-style Backlog.

Custom object types

Built-in types cover most use cases, but you can define your own to match how you actually think.

Examples:

  • Meeting — for meeting notes, separate from general pages
  • Project — for project containers in a PARA setup
  • Area — for areas of responsibility
  • Contact — for people you work with
  • Book — for a reading list
  • Recipe, Course, Idea, Decision — anything that benefits from its own type and colour

Creating a custom type

  1. Go to Settings → Types.
  2. Click New type.
  3. Configure the type:
FieldDescription
NameThe display name (required)
IconAn emoji or character shown in lists, the sidebar, and the graph
ColourPick from 10 presets (indigo, violet, pink, red, orange, yellow, green, teal, blue, slate) or use the colour picker for any hex value
PropertiesDefine a schema with custom fields (see below)
  1. Click Save.

Custom properties

Each custom type can define its own property schema. Add fields that make sense for the type:

Property typeDescription
TextSingle-line text
NumberNumeric value
DateDate or date-time
BooleanCheckbox (true/false)
SelectSingle choice from a list of options
Multi-selectMultiple choices from a list
FormulaComputed value from other properties
RelationLink to another object
URLWeb address
EmailEmail address

Each property can be marked as required (enforced on save) or sensitive (masked in table views with an eye-off icon).

Your new type appears in:

  • The ⌘N new object picker
  • The sidebar (under its section, if you've pinned it)
  • The type filter in Sets and databases
  • The graph view (nodes are coloured by type)

Bookmarks

The Bookmark type saves a URL and automatically fetches its metadata. When you create a bookmark:

  1. Enter or paste a URL.
  2. Aurora fetches the page title, description, Open Graph image, and favicon.
  3. The bookmark displays as a rich preview card with the image, title, description, and domain.

Click the card to open the URL in a new tab. Use Change URL to point to a different address, or Refresh to re-fetch the metadata.

Why types matter

Types let you filter by intent. A Set filtered to type = Project shows only your projects — not your notes, not your tasks. Types make the @ linker, the command palette, and the graph view dramatically faster to navigate as your workspace grows.

TIP

Don't over-engineer your types early on. Start with the built-ins. Add a custom type when you notice yourself tagging a group of pages with the same label and wanting to treat them differently.

Built with AuroraDocs.