Read the Monday digest
The weekly email on live data, rendered exactly as it will send.
The digest is the week in one message. It carries what is overdue, what is due inside seven days, what is on the clock over the next thirty, the schedule tasks due this week, up to five dates that are awaiting an event before they can resolve, and Waiting on you: every other kind of ask the Overview's Needs attention panel lists, from the same source, so the email and the screen cannot disagree about what is waiting. It is a snapshot of where the week stands, not a diff: it does not report what changed since last Monday.
This page renders that message on live data, exactly as it will send.
The paragraph at the top is written from the rows underneath it and kept for the week. An administrator whose own access covers the whole workspace can ask for it to be written again.
Who receives it
The digest is emailed on Monday mornings to members who have opted in under Settings. Because it is built once for the whole workspace and carries every project, it reaches only members whose own access covers the whole workspace. A project-scoped or external member sees no digest option they can turn on, so nobody is promised an email the sender would quietly withhold. A member whose role cannot see the schedule or documents is left out for the same reason, and Waiting on you is cut to each recipient's own role: a role with no money is not mailed a pay application.
How to
You open this to see what Monday's email will say before it says it.
- The digest is the Overview in an email: the same Needs attention and This week's work, sent rather than visited.
- The weekly email on live data, rendered exactly as it will send.
- What is overdue, what is due this week, and what lands in the next thirty days, across every project you can see.
- It is drawn for you rather than for the workspace, so two people on one workspace get two different emails.
- Nothing sends until you opt in, and that switch is in Settings, under Weekly digest, on the You half of the rail.
Related pages
Known limits
A single send is claimed per recipient, so a run in which the mail provider is down leaves every recipient able to receive next time rather than marking the week done. If a run stops halfway, the next one picks up exactly the people who have not been sent to yet and never mails anyone twice.
Asking for the brief to be written again needs an access level that covers every project in the workspace. A partial read forced into the shared weekly copy would overwrite it for everyone, so the request is refused rather than allowed to narrow what other people see.