Alexandria
Meeting notes work well in Alexandria when you model each meeting as a note and use a Meeting tag for the structured fields you want to review later.
In the desktop app, create a tag page for the meeting fields you want every meeting note to share:
Meeting.Meeting tag.date as datemeeting_type as selectattendees as multi-selectfollow_up_needed as booleanMeeting tag page, use View settings to show the property table when you want a spreadsheet-like review of all meetings.attendees is a multi-select property: it stores names as values on the meeting note.
Two-way links to Person notes are not supported yet. Attendees are not linked Person relations today.
For each meeting, create a normal note and apply the Meeting tag:
2026-07-11 Product sync.Meeting and pick the existing tag.date, meeting_type, attendees, and follow_up_needed.Use the note body for the actual notes and action checklist:
## Notes
- Reviewed launch risks.
- Decided to keep the beta scope unchanged.
## Checklist
- [ ] Send recap
- [ ] Confirm beta dates
Alexandria does not have a separate tasks feature today. For follow-ups, use a Markdown checklist in the meeting note body, or a boolean property such as follow_up_needed.
Create a normal dashboard note with Add page, for example Meetings Dashboard. In the editor, open the slash menu (/) and choose Link DB Table, then point it at the Meeting tag.
The table lists notes tagged with Meeting and shows the tag's properties.
Current limitation. Link DB tables show all notes for the tag. Saved filters, sorting, grouping, and column hiding are not available yet.