Databases hold structured records with typed properties. A record can also have document content, so information does not need to be split between an isolated spreadsheet row and an unrelated note.
Start with a collection
Create a database for a set of related items: reading notes, project tasks, inventory or ideas. Add properties that describe the collection, then create records. Use relations to connect records when the relationship matters.
Give records clear names. A record’s identity persists when it appears in another view or native section; changing a view should not require recreating the information.
Choose a view
Use the view controls to choose a table, board, calendar, list or gallery where supported. Saved filters and sorting make different questions easier to answer without duplicating records.
- Table: inspect properties and compare records.
- Board: group work by a useful property, such as status.
- Calendar: put dated records in time.
- Gallery: browse records as cards.
- List: keep a compact overview.
View configuration can include property-based colors. Color supplements titles and status labels; it is not the only way to identify a record.
Connect views to your workspace
Use inline database blocks in pages. Dated records can appear in Calendar, and actionable records can appear in Actions. Update the original record through these surfaces rather than managing separate copies.
When opening a record, choose a side panel, centered view or full page as supported by its controls. Properties and document content remain part of the same record.
Roles and changes
Workspace permissions determine who can read and edit shared databases. A different view, widget or agent connection does not bypass those permissions.
The agent bridge exposes reviewed operations for databases, records, fields and views. Inspect each tool’s schema before writing; required properties and revision fields come from the running server.