Omniscio documentation
Browse all documentation
  1. Getting Started19
  2. Sessions & Agents143
  3. Inbox & Notifications73
  4. Projects & Tasks104
  5. Automation & Scheduling78
  6. Knowledge & Memory29
  7. AI Features75
  8. Integrations116
  9. Plugins & Marketplace45
  10. Cloud & Teams55
  11. Settings & Customization82
  12. Account & Billing30
  13. Troubleshooting86
  14. CLI & API Reference29
  15. Legal & Policies5
  16. Uncategorised24

Mission Control email updates

Every Mission Control email is opt-in. A person turns on mention, assignment and reply emails, or a daily or weekly summary, in Mission Control → Settings → Email. The one exception is a single summary email in their third week, inviting them to set summaries up — and nobody is emailed about their own action, nothing is emailed twice, and every email has a one-click way to turn it off.

What it is

Status: built, waiting for the backend deploy described under For agents.

  • Mention email — someone @mentions you in an update or reply. Shows who, the item, the board and the first couple of sentences of the update, with an Open in Omniscio button.
  • Assignment email — someone adds you to an item's People column (not when they tick Mute). Shows who, the item, the board, and the item's status and due date when it has them.
  • Reply email — someone replies to your update. A reply that also @mentions you sends only the mention email. The bell shows a matching "replied" notice.
  • Summary email — daily or weekly at the hour you pick, in your own time zone: what you have not seen and were not already emailed about, grouped by board, up to 20 lines plus "and N more". Not sent when there is nothing to show.
  • Summary nudge — one weekly summary in a person's third week, only if they have never chosen a summary setting, asking whether they want one every week. Sent once, ever.

Where to find it

  • Mission Control → Settings → Email (above Appearance): Pause all email; Email me right away when someone mentions me / assigns me an item / replies to my update; Summary email Off / Daily / Weekly; Send it at (hour); On (weekday, weekly only). Everything starts off.
  • Item card → Updates tab — the Email settings link at the top opens that card.
  • Inside every email — a "Turn off … emails" link. It opens a page with one button to confirm, so a mail scanner that follows links never unsubscribes anyone. Mail apps' own Unsubscribe button turns it off in one click.

How it behaves

  • Instant emails arrive within about a minute. Several notifications for the same person on the same item within ten minutes become one email that says how many updates it covers.
  • At most 25 instant emails per person in a rolling day; the rest wait for the summary or the bell.
  • An email never names an item from a board the person can no longer open, or from another account.
  • A send the mail service refuses is recorded as failed and tried again on the next run.
  • The nudge clock starts the first time the person opens Mission Control, not when they were invited. Choosing any summary setting, including Off, or pausing all email means no nudge.

For agents

  • Backend routes (Mission Control backend, mounted under its prefix): GET/PUT /email-preferences (signed-in caller's own row), GET/POST /email/unsubscribe (signed link), GET /open/board/:boardId (launcher page), POST /internal/email/run (the job).
  • Going live needs three things on the Mission Control backend deploy:
    1. MC_EMAIL_LINK_SECRET — signs the turn-off links. Without it the job sends nothing.
    2. MC_EMAIL_JOB_SECRET — the job endpoint answers 503 until it is set.
    3. A Cloud Scheduler job calling POST <APP_INVITE_BASE>/internal/email/run every minute with the header x-mc-email-job-secret: <MC_EMAIL_JOB_SECRET>.
  • Where they live. Both secrets are Secret Manager secrets in the backend's Google Cloud project, named exactly as above, and amc-back/deploy.sh binds them (NAME=NAME:latest). That list replaces the service's bindings on every deploy, so a secret bound only by hand is dropped by the next deploy. The scheduler job is mc-email-updates-run in that same project (us-east1), posting to https://amcback.jls.dev/monday/internal/email/run; pause it with gcloud scheduler jobs pause mc-email-updates-run --project=<that project's id> --location=us-east1.
  • Mail goes out through the existing SMTP2GO transport and shares its allowance with invites and password resets; the 25-a-day ceiling bounds it.
  • Replying to an email posts an update. Mention, assignment and reply emails are sent with a per-item reply address minted by the reply-by-email intake (mintReplyAddress); replying to one posts the reply as an update on that item, and the email says so. When the intake is not configured no address is minted, the email replies to support@omniscio.com, and the reply line is left out. Summaries are not tied to one item, so they carry no reply address.
  • Rules: mission-control-email-updates-contract.md.

Related

mission-control.md is the parent page. The desktop Ops Engine's own per-board email setting (pm-notification-preferences.md) is a separate local system and is unchanged.

Last verified 2026-10-24