Notifications
Notifications tells the right people when a record moves into a status. For each kind of record an admin sets who is told for every status, once for the organisation and, if needed, differently for one project.
Where it lives
- The organisation default: Configuration → Notifications.
- A project override: Config → Notifications inside the project.
What you can set
| Record | When it becomes | Who can be told |
|---|---|---|
| Diary | submitted, approved, confirmed, sent back to draft | staff; clients on the first three |
| Prestart | started, saved, published | staff |
| Docket | sent back to draft, submitted from the field, submitted, reviewed, confirmed | staff |
| Day works sheet | saved, raised | staff |
| Roll call | started, completed | staff |
“Diary approved” is the engineer’s approval step.
Who can be told
For each row, pick any mix of:
- Everyone in a role: for example every Engineer on the project. People who join or leave the role are picked up automatically.
- Named office staff, listed under their role.
- Client contacts, listed under their company. Clients are only offered on the diary rows a client can see.
Nobody ticked means nobody is told. Every row starts empty, so nothing is sent until you set it up.
Organisation default and project override
A project follows the organisation default for a row until you change that row on the project; it then shows Overridden and owns its own list, which may be empty (nobody). Use organisation default returns the row to Inherited.
What gets sent
- Diary and prestart changes are emailed straight away.
- Dockets, day works sheets and roll calls are grouped: one email per row per project every five minutes, with a count and the first ten names, so a bulk change does not flood anyone.
- The email has a button that opens the list for that kind of record.
- Only people who are still active and still on the project receive it, even if they were ticked earlier.
Issues keep their own notification lists on the Issues screen.