Follow a project
Open project details and choose Notify me about this project. Notifications on confirms your subscription; Stop notifications unsubscribes you. These are your own preferences. Viewers can use them too.
Notifications cover changed completion forecasts, target missed/recovered, hard deadline risk/recovery and project completion. Identical outcomes do not send email. One planning operation produces at most one message per changed project and subscriber. Changes to a new project without a previous forecast do not send movement messages.
Configure organisation email
Administrators open Settings, then Manage email settings. Choose SendGrid API or authenticated SMTP, and enter the From address/name. SMTP supports required STARTTLS, TLS on connect or None; use encryption for production credentials. The username may differ from the From address.
Saved credentials are protected. They never reappear in the form. Leave replacement fields blank to retain them. Save before using Send test email: the test uses the selected, enabled saved configuration. Provider acceptance does not guarantee inbox delivery; check the destination and spam folder.
The installation operator must configure the public HTTPS application URL and preserve the Data Protection key ring across deployments. An administrator cannot enable email until that URL exists.
Reliable delivery
Project email is queued in SQL alongside forecast history, then sent in the background. Disabled organisation email pauses delivery; subscriptions and pending messages remain. Unsubscribing cancels pending messages. Revoked workspace access or archived/deleted projects prevent delivery when queued work is claimed.
Temporary failures receive up to six attempts with increasing delays. Invalid credentials/configuration stop that message; fixing settings allows future messages, but does not replay previously failed messages. Your planning changes never depend on the provider being available.
Emails use calendar hours on the London planning clock, not invented working-day equivalents. Reasons use the explicit planning change where it can be attributed reliably. Compound or uncertain changes use a truthful recalculation explanation.
SQL claiming prevents two active workers from claiming the same message. A crash after provider acceptance but before recording success can still result in a duplicate after lease expiry. Email delivery is not exactly once.