Skip to content
flowplanDocumentationCommunityMarketplaceStart page

Databases

Databases

A database is a collection of records with properties. The same records can be shown as a table, board, calendar, timeline, gallery, list, feed, chart or form.

13 min read

On this page
  1. Create a database
  2. Records
  3. Sub-pages of a record
  4. Move a page into a database
  5. Turn a record into a page
  6. Copy and move records
  7. Large databases
  8. Filter, sort, group
  9. Recurring records
  10. Repeating tasks
  11. Date reminders
  12. Permissions per record
  13. Automations and workflows
A roadmap database as a board: the views Table, Board, Calendar and Timeline, below them filter, sort and grouping by status, and the columns Backlog, Planned, In progress and Done with cards showing person, priority, team and date
A database in the board view, grouped by status.

More on this topic: Database properties

Create a database

New page → Database shows the Kind right below as one row to choose from, with the properties of the chosen one underneath:

KindPropertiesFirst view
TasksTask, Status, Priority, Due, Assignee, TagsTable "All tasks", plus board, calendar, timeline …
DocumentsTitle, Tags, Created, EditedList "All documents" (last edited first), gallery, table; records open as a full page, empty properties are hidden
ContactsName, First name, Last name, Company, Position, E-mail, Phone, Mobile, Street, Postal code, City, Country, Birthday, TagsList “All contacts” (by last name), Table, calendar “Birthdays”, Gallery; records open as a profile page with a contact card – see Contacts
Emptyonly a titleTable

Below are Your templates: saved database templates, such as your own "Notes (PARA)" database with relations and views. The device remembers the last choice. Alternatively use a template, such as "Tasks" or "Projects", or import a CSV file (see Import, export and versions).

Records

  • New at the bottom of the table or at the top right creates a record and opens it with the title selected – just start typing, Enter saves.
  • Editing: in the table Enter saves numbers too; a double-click on a multi-select only opens it without ticking an option. Esc closes an open record – what you typed into the title or properties stays saved.
  • A click on the title opens the record as a page: the title at the top to edit directly, the properties below it, and below them a full document with the same editor as every other page – including comments, version history and editing together.
  • Open records as (sliders at the top of the record → layout, for all records of the database; a view can choose differently under Configure view): Side peek to the right of the view, Centred as a dialog over the view (the default) or Full page – the record then fills the content area next to the sidebar like any page, with no database behind it.
  • Side peek beside the view New in 0.10.2, in the :beta image: in a timeline it docks beside the view, which narrows and stays clickable – another bar switches the record, ↑/↓ step through the view, Esc closes. Drag the left edge for its width (kept per device). Tables, boards and lists choose Beside or Over under Configure view → Side peek. Below 1000 pixels the record opens as a page.
  • Order of properties Since 0.9.8: whoever may change the database's structure reorders the properties in an open record – drag the handle (⋮⋮), or tap or click it for To the top, Move up, Move down and To the end (with the keyboard also ⌥↑/↓ on the handle). The order applies to all records of the database and everyone who sees them – also as a full page, in shared records, in print and in a record's export. Tables, boards and other views keep their own column order; new properties go to the end.
  • Open as page (arrows at the top of the record) shows a record once as a full page, in a new tab with ⌘/Ctrl-click or the middle mouse button. Get back through the path in the top bar, the back button or the arrows at the top of the record (back to the side peek or the dialog).
  • Also at the top right of a record: the star for favourites (in the sidebar a favourite opens the record as a full page), Copy link for the record's address, Share for links and the publication of only this record (Share a single record), the lock for the record's permissions and the sliders for the layout of all records. Icon and Cover appear when the pointer is over the title.
  • Reading mode (book icon at the top of the record or ⌘⌥E) opens a record's text for reading only, as for pages; the device remembers it per record. Opened as a full page, Full width uses the whole screen – the properties keep a readable width, the text gets the space.
  • An open record has its own address (/#page=<database>&row=<record>, as a full page with &full=1). It can be shared, bookmarked or linked in texts with @; the browser's back and forward move between database, dialog and full page. Below the properties, Linked from shows which records refer to it through a relation and which pages and records link to it in their text.
  • Record templates give new records properties and content. One template can be the default for new records.
  • Select several records (checkboxes on the left) and edit, duplicate or delete them together – up to 500 at once. Flowplan saves a state beforehand that can be restored from the version history.
  • Deleted records sit in the database's trash and can be brought back – with their versions, the comments visitors left through a share link and the reactions on comments. This also works when a record linked two-way has been deleted meanwhile; only that link is dropped. Right after deleting it is quicker: Undo in the notice at the bottom (or ⌘Z while it shows). A bulk edit of several records, a record dragged into another column, a removed date and a deleted property can be taken back the same way.

Sub-pages of a record

A record can hold pages of its own – call notes, a specification and flowcharts below a requirement, for example:

  • Add sub-page below the record's document (in the dialog and as a full page) creates a page below the record and opens it. Its Sub-pages are listed above.
  • Existing pages go there with Page actions → Move (the database as parent page, then choose Below record) or by drag and drop onto the record's sub-pages or onto the record in the sidebar. Several selected pages can be moved onto a record that already has sub-pages.
  • In the sidebar, an expanded database shows the records that have sub-pages, with their sub-pages; the other records stay in the database. The path in the top bar shows database → record → sub-page.
  • Sub-pages follow the record's permissions: whoever does not see a private record does not see its sub-pages either; a read-only record makes them read-only for editors. Adding or moving pages there needs edit rights on the record.
  • Deleting the record moves its sub-pages to the trash with it; restoring brings them back, deleting for good removes them. Move to … another database takes them along; Convert to page makes them sub-pages of the new page. Duplicate and Copy to … copy the record alone; a copy of the whole database includes the sub-pages.
  • Stand-in pages from an earlier Notion migration (a same-named page holding the sub-pages) are dissolved by moving their sub-pages below the record and deleting the empty page.

Move a page into a database

Page actions → Move into database … turns a document page into a record of a database you may write to – for example to bring grown documentation into a notes database:

  • Title, icon and cover become the record's title, icon and cover, the content its document; files and images stay the same files (they then belong to the database).
  • The page's tags go into the database's (first) multi-select with the workspace's tags, if there is one and you may change it.
  • Comments, text comments, tasks and versions come along; favourites become record favourites.
  • Links to the page in all pages and records of the workspace then point to the record.
  • Sub-pages stay pages and become sub-pages of the record; with a database in another space they move up one level. Permissions for people set on the page keep applying to them.
  • Sharing of only this page (permissions for people, share links, publication) ends – the dialog lists it first; the record follows the database's permissions. The database's default record template applies.
  • The page itself goes to the trash.

Turn a record into a page

The other way round, Turn into page … makes a record a document page again – in the … menu at the top of the open record or with a right-click on the record. You need edit access to the record and write access at the target location:

  • Title, icon and cover become the page's title, icon and cover, the record's document its content; files and images stay the same files (they then belong to the page).
  • The properties stay as a short "Property: value" list at the top of the page (readable in a Markdown export too); in the dialog you can drop them instead.
  • The tags from multi-selects with the workspace's tags become the page's tags.
  • Comments, text comments, tasks and versions come along; record favourites become page favourites.
  • Links to the record in all pages and records of the workspace then point to the page – @ links and backlinks keep working.
  • The page goes where the database is, or to another location of your choice, and follows its permissions. The record's own permissions and relations from other records to it end – the dialog lists them first.
  • The record itself goes to the database's trash and can be brought back.

Copy and move records

A right-click on a record – in a table, board, list, gallery, calendar or timeline – opens its menu: Open, Duplicate, Copy to …, Move to …, Turn into page … and Delete. When several records are selected, the menu applies to all of them; the selection bar also has Move / copy to ….

Copying records: with records selected in the table view, Copy in the selection bar (or ⌘/CtrlC while no text is selected) puts them on the clipboard – with the view's visible columns as the header row, in the table's order. Pasted into Excel, Numbers or Google Sheets, every value lands in its own cell; in a document it becomes a table. Values come out as the table shows them: numbers in the column's format, select and person columns by name, relations by the record's title, checkboxes as Yes/No.

In the dialog you choose the target database in the same workspace:

  • Copy creates new records – with properties, content, icon and cover. Files and images of the source database are copied too, so the copy does not depend on the source. Only files that belong to the source database, that you may see and that are not in the trash are copied; a reference to any other file stays a reference and keeps that file's permissions.
  • Move takes the record itself: content, comments, version history, tracked time and Git links stay with it. In the new database it gets the next number (ticket ID).
  • Properties are matched by name, the title always to the title. Compatible types are converted (text ↔ e-mail, select ↔ multi-select, number → text …); missing select options are added to the target. Create missing properties in the target adds properties the target does not have yet.
  • Calculated values (formulas, rollups, progress, created/edited) are worked out again in the target.

Dragging is quicker: drag records by their handle (with the mouse also by the card) onto a database in the sidebar to move them there – the target database is highlighted; hold Alt when you let go to copy them instead. Flowplan saves a state of the source beforehand.

Large databases

Tables, lists and galleries first show 100 records; the next 100 follow as you scroll, and groups and board columns have Show more. Search, filters, sorting and column calculations still always apply to all records. This way even databases with thousands of records open in a fraction of a second.

Filter, sort, group

Every view has its own settings:

  • Filters with AND/OR groups; for date fields also relative periods ("this week", "last 30 days") that update themselves every day.
  • Dates and time zone: on Created at, Edited at and date fields with a time, is, is not, before, after, on or before, on or after and is between count the day the moment falls on in the filter's time zone – a record from 11:30 pm belongs to that day, not the next. The default is your browser's time zone; it shows in the filter and can be changed there, as for relative periods. Dates without a time stay calendar days. Older filters keep using the UTC day until you edit them. The same goes for conditions in automations.
  • Sorting by several properties. People, Created by, Edited by and sprints sort by name, relations by the title of the linked record – the way the table shows them.
  • Grouping by almost any property (except files and checklists), with up to five levels in tables and lists; boards show the second level as rows (swimlanes).
  • Search within the database, also in the text of the record documents.
  • Column calculations below table columns: sum, average, median, minimum, maximum, percentages, earliest and latest dates and more.

Recurring records

Date fields can repeat daily, weekly, monthly or yearly. Calendar and timeline show the occurrences; it remains a single record. If needed, a single occurrence can be detached as a record of its own.

Repeating tasks

For tasks that are ticked off one by one each time (“monthly closing”, “server updates”), set a rhythm in the record under Repeating task: daily, weekly (optionally on certain weekdays, e.g. Mo, We, Fr), monthly or yearly, each every N days, weeks, months or years. The setting reads as one sentence, e.g. “Weekly · every 1 weeks · Mo · counted from Due”. Counted from only appears when there are several date properties and sets which date the next record counts on from; below it, a hint says when it follows. Since 0.9.8

As soon as the record is done (status or checkbox, see When is a record done?), Flowplan creates the next record: a copy with the status it had before, the chosen date on the next occurrence and every other date field moved by as many days. The rhythm moves to the new record; reopening and completing the old one again creates nothing more.

  • Month ends are clamped but the day is kept: 31 January → 28 February → 31 March.
  • 29 February becomes the 28th in common years and the 29th again in leap years.

New records at fixed times – whether or not the last one is done – come from scheduled automations.

Date reminders

In a record, everyone can set a personal reminder for every filled date field – for times at the appointment or 5 minutes to 1 week before, for all-day dates on the day or 1, 2 or 7 days before at 09:00. Reminders appear in the inbox and as a push notification and do not change the record.

Permissions per record

The permissions icon at the top of a record restricts a record beyond the permissions of the database:

  • Same as database: the default.
  • Read-only record: only its managers (page owners and the person who created the record) and people it is explicitly shared with may change it.
  • Private record: only its managers and people it is shared with see it – together with its comments, tasks and files (in the file list, search, media library, copies, templates and backups).

Shares with people or groups never go beyond their role on the database page.

Automations and workflows

Recurring steps of a database – set a date, notify, apply a template – are done by automations under … → Automations. For longer flows with branches, waits, approvals, AI, e-mails or other services there are workflows; every rule can be extended into one with Open in canvas.

Was this helpful?
YesThanks!
No – tell us what's missing

Found a mistake or something missing?Edit on GitHub