Notifications and activity history
Follow work that needs attention and understand who changed a record.
Use notifications as a work queue
Notifications draw attention to events such as pending approvals, overdue work, budget warnings, assignments and mentions. The events you receive depend on your role, project involvement, available features and notification settings. A notification is a prompt to open the source record; it is not a substitute for checking that record’s current status.
Open the notification bell or Notifications page, choose an item to follow its link where available, and mark it read after reviewing it. A record may have changed since the notification was created. If a link is unavailable, find the item by its number in the relevant module.
Separate the alert from the history
Activity history helps authorized users trace actions such as creating, updating, approving or deleting records. Filter it by the available criteria, then compare the event time, actor and record. Use the source document and its own history to understand the business effect; an activity row alone does not prove that money moved or goods arrived.
Email and in-app delivery are separate. Your organization can limit automated email, and the platform has its own delivery switch. Comment mentions are in-app only. Do not assume an email was sent just because an in-app notification exists.
Example: a delivery verification notification tells the storekeeper to review the receipt; the delivery record, inventory movement and activity entry together explain what was received and by whom. If a notice looks wrong, send support the record number and time rather than forwarding confidential files unnecessarily.