Notes, replies and decisions
The three things you write into a feed, and how they differ in practice.
A note, a decision, and the task one of them makes
A note is talk. A decision is a note deliberately marked as one and rendered differently in the feed — the thing you go looking for six months later.
Tasks come from here too, but not automatically: only a post marked with the composer's task icon creates a task on the board. A plain note is conversation and creates nothing.
An empty note is refused.
Replying to an item
A reply always attaches to a live item in the same feed. Replying from one feed to an item in another is refused — unless that item has been cross-posted and is genuinely present in the destination feed.
Because an organisation's feed rolls up its engagements' items, replying from the organisation page to an engagement's item is entirely legitimate.
If the parent item is deleted, the replies are not lost; they detach and remain as replies to a deleted message.
Who can do what
| Action | The author | An admin | Everyone else |
|---|---|---|---|
| Read | |||
| Edit the body | |||
| Delete | |||
| Reply |
Deleting a note takes its open task with it
Delete a note that spawned a task while that task is still open, and the task goes too — a task whose source has been erased tells nobody anything.
A task already ticked stays: it records a decision somebody made, and it only loses the link back to its source.
Read this next
- Contacts & engagementsWhat a feed isA timeline that attaches to the record, not to the person. The memory of the system.
- Work, tasks & PulseWhere tasks come fromFour sources, and one rule that keeps the board from filling with noise.
- Contacts & engagementsVoice notesA minute of talking instead of five of typing — and what happens if transcription fails.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.