Skip to content
YepstaYepsta Help Centre

Understand Project Notifications

Project notifications tell the responsible person that an authoritative event occurred or action is due. They do not grant access: every link still checks tenant, location, assignment and record permissions when opened.

Events that can notify people

Section titled “Events that can notify people”

Depending on enabled capabilities and Notification Centre → Preferences, Projects can notify for:

  • Draft creation, Project assignment, team membership and task assignment;
  • Agreement sent, viewed, signed, declined, revised or voided;
  • intake requested, reopened or submitted;
  • setup readiness, start and lifecycle changes;
  • billing-stage readiness and relevant Invoice/Payment effects;
  • review requests, decisions, comments and annotations;
  • final delivery release;
  • Change Order requests and responses;
  • client updates, messages, action items and client uploads;
  • time, timesheet, budget and resource-planning events;
  • retainer cycle, usage, billing, closure and renewal events;
  • saved reminder recipes and weekly digest.

Not every event uses every channel. Delivery depends on the configured event, recipient, available provider, preference and consent at send time.

Understand recipients

Section titled “Understand recipients”

Staff recipients come from the Project manager, members, task assignments, workflow responsibility and configured automation audience. Client recipients come from active explicit stakeholders with the exact responsibility and access required by the source record.

A broad Customer Account link does not make someone an Agreement signer, intake respondent, reviewer or action-item assignee. Those are explicit assignments.

Share a Client Update

Section titled “Share a Client Update”

Client Updates let the sender select eligible email, SMS or WhatsApp delivery where available. The published update remains in the Customer Account even when a channel cannot deliver. Recipient preferences and consent are respected.

Distinguish event notifications and reminders

Section titled “Distinguish event notifications and reminders”
  • An event notification follows a real state change, such as an Agreement being sent or a task being assigned.
  • A reminder automation evaluates an existing due/waiting condition on a schedule.

Pausing Project reminders does not undo event history or automatically suppress every direct notification.

Troubleshoot missing delivery

Section titled “Troubleshoot missing delivery”

Check:

  1. the intended recipient is active and explicitly assigned;
  2. the source event actually occurred and is current;
  3. the Project or recipe is not paused;
  4. the relevant event and channel are enabled under the correct Customers or My Business audience;
  5. the recipient’s address or mobile is verified and usable;
  6. preference and consent allow the channel;
  7. the recipient still has access to the source record.

For a client, the Customer Account remains the best place to confirm current Project responsibilities even if an external channel is delayed.

Use Notification Centre → Delivery History to inspect the external dispatch. The source Project record remains authoritative even when the notification is Failed or Skipped.

Last reviewed: