Notes

What a note attaches to

Each note has one subject, of seven kinds: a record, a file, a model, an operation, a schedule, one of your users, or the project itself, for a general task with no record to hang on. The record editor has a notes panel for the record you have open.

One field, or one passage

A note on a record can point at a single field with anchorField, and at one passage inside that field's prose. The passage is identified by the persistent id of its node in the stored content, and the note keeps the selected text, so it still reads correctly after the passage has moved.

Replies, mentions and settling

Replies thread under a note and nest to any depth. An @mention notifies a team member and has a status of its own (pending, seen, acknowledged, completed or dismissed) and, if you set one, a due date. Each person has a view of their mentions: pending, past due and completed this week.

Each note is settled individually, optionally with a reason, and settled notes are hidden until you ask for them. The API and the CLI call this resolving. A note with an assignee is a task.

The inbox

The console keeps an inbox for each project, listing every note with its subject, its author, its state and the date it was added. Filter by open or settled and by kind of subject, or search the full text of every note, replies and settled notes included.

Who can see a note

A note is visible to everyone in the project unless its author makes it private, which limits it to the author and the people they mention. Notes are scoped to a project in storage, so a member of one project cannot see another project's notes through the console or the API. foir notes works the same threads from the command line.