Notifications and activity
The bell, the project's activity feed, and choosing which notifications are emailed.
The bell
The bell in the status bar (in the top bar on a phone) lists what other people did that concerns you. The number on it is how many you haven't read.
You get a notification when someone:
- mentions you in a comment with
@and your name - replies in a comment thread you started or took part in
- shares a project with you
- accepts a workspace invitation you sent
- asks you to review a note, as one of its required reviewers
- approves a note you sent for review, or asks for changes
You are never notified about your own actions, and one-click reactions don't notify anyone.
Click a notification to open the note it is about. If it is about a comment, the Comments tab opens on that thread. Notifications from your other projects are in the same list; clicking one takes you to that project. Opening a notification marks it read, and Mark all read clears the count.
A notification holds names and titles only: who, what kind of thing, and which note. It never contains the text of a comment or a document.
The activity feed
Open Activity from the ribbon, or run "Open activity feed" from the command palette. It lists what happened in the project, newest first:
- notes created, renamed, moved to the trash and restored
- comments added
- versions saved with a name, and versions restored
- releases cut
- the project being shared, with the role but not the person's address
Everyone who can open the project sees the same feed. Titles are shown as they were at the time, so a renamed note appears under its old name in older rows. Click a row to open its note, if it still exists.
Typing isn't in the feed. For how much was written and when, see Writing goals.
Notifications can also be emailed. Open your account menu, choose Your settings, and under Email notifications pick one:
| Setting | What you get |
|---|---|
| A daily digest | One email a day listing what you haven't read. No email on a day with nothing new. This is the default. |
| Each one | An email when it happens, up to twelve an hour. Anything past that goes into the next digest. |
| Off | No notification emails. |
Something you have already read under the bell is not emailed. Invitations and sharing emails are sent whatever you choose here, because they carry the link you need to get in.
Like the notifications themselves, the emails say who did what and where, with a link, and nothing from the text.
On the hosted version the number of notification emails a day is limited. On a busy day some may arrive in the next day's digest instead; nothing is lost from the bell.
If you host Plotra yourself
The digest is sent when something calls /api/cron/digest with the CRON_SECRET you set. The repository includes a GitHub Actions workflow that does this once a day; any scheduler that can make an HTTP request works too. Without CRON_SECRET no digest is sent, and without RESEND_API_KEY emails are written to the server log instead of sent.