Notes & Comments
Notes let your team collaborate directly on content. Attach comments to any record, mention team members, track action items, and resolve discussions — all without leaving the admin dashboard.
Overview
Notes are threaded comments attached to records. Your team can leave feedback, ask questions, or flag issues directly on the content they are reviewing.
Blog Post: "Summer Sale Announcement"
+-- Note: "Can we update the hero image?" (unresolved)
| +-- Reply: "Done -- uploaded new image" (resolved)
+-- Note: "Legal team needs to review pricing copy" (@sarah, due Friday)
+-- Note: "Looks good to publish!" (resolved)Key concepts:
- Notes attach to a specific record and optionally to a specific version.
- Threaded replies keep conversations organized under the original note.
- Mentions tag team members and create trackable action items.
- Priority levels flag the importance of a note.
- Resolution marks a discussion as complete.
Note Properties
| Property | Description |
|---|---|
content | Rich text content (Lexical JSON format) |
modelKey | The model key this note is attached to |
recordId | The specific record ID |
versionId | Optional — ties the note to a specific version |
parentNoteId | For replies — creates a threaded conversation |
metadata | Priority, pinned status, attachments |
In the Admin
Creating Notes
- Open any record
- Click the Notes panel
- Write your comment (supports rich text)
- Optionally @mention team members
- Click Post
Threaded Replies
- Click Reply on an existing note
- Write your response
- The reply appears nested under the parent note
Threads keep conversations contextual — each discussion stays with the note that started it.
Mentions
Tag team members with @mentions to notify them and create action items. Mentions have a status workflow:
| Status | Description |
|---|---|
PENDING | Mention created, user not yet notified |
SEEN | User has seen the mention |
ACKNOWLEDGED | User has acknowledged the mention |
COMPLETED | User has completed the requested action |
DISMISSED | User dismissed the mention with a reason |
You can also set a due date on mentions for time-sensitive tasks.
My Mentions Dashboard
View all your mentions across the project:
- Pending — action items waiting for you
- Past due — mentions with expired due dates
- Completed this week — recently resolved items
Priority Levels
Set priority levels to flag important notes:
| Priority | Use Case |
|---|---|
LOW | Minor suggestions, nice-to-haves |
NORMAL | Standard feedback (default) |
HIGH | Important issues that need attention |
URGENT | Blocking issues that need immediate action |
Resolving Notes
When a discussion is complete or an issue is fixed:
- Click Resolve on a note
- Optionally add a resolution note explaining what was done
- Choose to resolve the entire thread or just the parent note
Resolved notes are hidden by default but can be shown with the Include Resolved filter.
Searching Notes
Find notes across your project by:
- Content — full-text search across all notes
- Record — notes on a specific record
- Author — notes from a specific team member
- Status — resolved or unresolved
Via the CLI
# List notes (with optional filters)
foir notes list
# Get a specific note by ID
foir notes get <id>
# Create a note on a record
foir notes create --data '{
"modelKey": "page",
"recordId": "rec_abc123",
"content": "Please review the updated hero section before publishing."
}'
# Create a threaded reply
foir notes create --data '{
"parentNoteId": "note_abc123",
"content": "Looks good, approved."
}'
# Resolve a note
foir notes resolve --data '{
"noteId": "note_abc123",
"resolution": "Hero image updated and approved."
}'
# Delete a note
foir notes delete <noteId>Best Practices
- Use mentions for action items — @mention the person responsible so it appears in their dashboard.
- Set due dates on time-sensitive mentions to track deadlines.
- Resolve when done — keep the notes panel clean by resolving completed discussions.
- Use priorities sparingly — reserve
URGENTfor truly blocking issues. - Reply in threads — keep conversations organized by replying to existing notes rather than creating new ones.
- Attach notes to versions — when reviewing changes, tie your notes to the specific version for context.