Skip to main content

Notifications & assignee

Moments live inside a team, not just in one head. The person who captures a Moment often isn't the person who'll turn it into content. The person who requests a Moment often isn't the person who'll capture it. Two mechanics keep everyone on the same page: the assignee field and the notification stack.

The assignee​

Every Moment has one assignee — the team member who's responsible for turning that Moment into content. This is separate from the author (who captured it) and the requester (who asked for it, if it came from a request).

How the assignee gets set:

  • During capture — the AI capture chat can ask "who should turn this into content?" and set the assignee based on your answer. Especially useful when the person on the phone is different from the person managing content.
  • From the review screen — before saving on mobile, tap the assignee field to pick a teammate.
  • From the desktop Moments page — on the row's three-dot menu → Change assignee.
  • When it comes from a request — the requester is set as the assignee by default (they're the one who wanted the Moment for something specific).

If no assignee is set, the Moment shows as unassigned and doesn't ping anyone specifically. It shows up in the shared list for anyone to grab.

The notification stack​

When something happens to a Moment, notifications go out to the right people. Three flavors:

Moment saved​

Fires when a new Moment is saved (either directly, or when a Requested Moment is captured).

  • Author — a quiet confirmation in the in-app bell. No push, no email. The author knows they just saved it.
  • Assignee (if different from the author) — an "assigned to you" ping: in-app bell + mobile push + email. Louder because they didn't do the capture and need to know they have something to work with.
  • Requester (if this was a Requested Moment) — a "your requested Moment is ready" notification: in-app bell + mobile push + email.

Moment requested​

Fires when someone requests a Moment from a teammate.

  • Assignee — the person the request is aimed at gets an in-app bell + push + email, with a link that opens the request directly in the mobile capture chat.

Moment nudge​

Fires for Drafts that have been sitting untouched for a while.

  • Author — up to two gentle mobile pushes reminding you to finish or save the Draft. If ignored, empty Drafts get cleaned up automatically. Drafts with content are kept and auto-saved as regular Moments.

Where notifications open​

Tapping a notification does the right thing on each device.

  • From mobile push — opens the Moment (or the request) directly in the mobile capture chat, with the assistant already in the right context.
  • From in-app bell (desktop) — opens the Moment card on the Moments page. If it's a request, opens the request dialog to view the details.
  • From email — a universal link. Tapping on mobile opens the app; tapping on desktop opens the web app. Same destination in the end.

Turning off notifications​

Notifications for Moments follow the account-level notification preferences. To adjust:

  • Mobile push — Settings → Notifications on the mobile app
  • Email — Account settings → Notification preferences on the web app
  • In-app bell — always on. Can't be silenced; it's not a push.

Team leads: even if a specific person mutes push, the request they receive still ends up in their in-app bell and their inbox. The mute is about volume, not about being cut out of the loop.