You are never emailed about something you did yourself. The person who caused an event is always removed from its audience.
Every email is tied to a project you're a member of. DocuBuild sends no marketing mail.
Three controls, three scopes: per-project events (Admin), your own reminders (you), and the unsubscribe link in any reminder.
What you get emailed about
| Group | Sent when | Who gets it |
|---|---|---|
| Requirements | A condition is assigned to you, its due date is approaching or has passed, or someone chases it. | The condition's owners. |
| Documents | A document is uploaded, a new version replaces one, a document is renamed or deleted. | People connected to that condition or folder. |
| Approvals | Something needs your review; a document is approved, rejected, or force-approved; a peer completes a step. | Approvers on the current step, and the uploader. |
| Comments | Someone mentions you, or replies in a thread you're part of. | The people named, plus the thread's participants. |
| Joining | You're invited to DocuBuild or added to a project. | You. |
| Signing in | You request a code or a link. | You — and only when you asked. |
Every one of these carries a link that signs you in and lands you on the thing it's about. That's usually the fastest way to act on it — see signing in.
The three controls
Project settings → Notifications. Events are grouped into Requirements, Comments and Approvals, and each one has two independent switches: whether it notifies people inside the app at all, and whether it also goes out by email.
This is the right lever when a whole project is too noisy — turning off email for a chatty event type quiets it for everyone, without losing the in-app notification. Changes apply to that project only.
Account settings → Reminder emails. A single switch covering the daily reminder about conditions awaiting your attention, across every project you're on. Off means off everywhere.
It only affects reminders. Direct notifications — you were assigned something, someone needs your review — keep arriving, because they're addressed to you rather than swept up in a daily summary.
Every reminder email carries one. It asks you to confirm, then switches the same preference as control 2 — useful when you're on your phone and don't want to sign in to do it.
Why you're getting fewer emails than you expected
- You caused it. The actor is always removed from an event's audience. Uploading a document, then wondering why no email arrived, is the most common false alarm — and it makes testing notifications on your own account misleading. Ask a colleague to check.
- It was part of a batch. Uploading thirty documents sends one email covering all of them, not thirty — see uploading a lot of files at once.
- The daily reminder had nothing to say. It only covers conditions that are still waiting on evidence. Once a document arrives, that condition drops out of the reminder even though it's still open.
- An Admin turned that event's email off for the project.
Sign-in codes and links can't be switched off, and shouldn't be — they're only ever sent because someone asked for them, and they're how you get in. If you receive one you didn't request, that means somebody typed your address into the sign-in page. The code itself is useless to them; tell us if it keeps happening.
Not receiving any of it?
If DocuBuild email isn't arriving at all, it's almost always filtering rather than a preference:
| 1 | Check your junk folder, and mark one as "not junk" so later ones land properly. |
| 2 | Ask IT to allow docubuild.io. Construction firms often filter external senders hard, and notification mail is exactly the shape that gets caught. |
| 3 | Check which address you were added under — mail goes to the address on the project, which isn't always the one you read. |
| 4 | Still nothing? Email support@docubuild.io and we'll check whether it was sent and what happened to it. |