Join the LadVen OS testing programRequest a demo
Skip to main content

Notifications

Notifications in LadVen OS help you notice assignments, comments, due date changes, mentions, rework returns, automation actions, and other events that require attention.

A notification does not replace work inside the task card. It only shows that something changed in the work context. A decision, question, result confirmation, or reason for a change should stay in the task, comment, file, checklist, or related object.

Where to find them​

Notifications are gathered in the bell in the portal's top bar. It opens a list of unread events grouped by source — tasks, CRM, chats, and system-wide. From any notification you jump to the related object instead of resolving the event in the list itself.

  • Notification bell — an unread counter and a panel of recent events, updated in real time;
  • Jump to the object — a notification opens the task, comment, deal, email or document it concerns;
  • Activity feed — for a broader stream of activity, use the Feed section, not the bell.

Notification types​

Notifications arrive on events from different modules. The main groups:

  • Tasks — assignment, task changes, checklist edits, a new comment and reaction, an approaching or reached deadline, a reminder;
  • Chats and calls — a new message, a mention, an incoming and a missed call;
  • CRM — deal assignment (with a pop-up notification of who assigned it and an "Assigned to you" marker on the deals board), a new message and mention, a comment, a stage change and a deal field change;
  • Mail — a new email in a connected mailbox;
  • Documents — a document update, inbound documents and approval requests.

An event has a priority (normal or elevated) — it helps separate what needs attention now from the background stream.

Delivery channels​

The same event can arrive in several ways. Tune the channels so important things are not missed and the background does not distract:

  • In the app — the bell and the unread counter, in real time while the portal is open;
  • On the desktop — system notifications when the portal tab is not active;
  • Push in the browser or app — for events you cannot miss outside the portal (require notification permission).

If a channel is not needed or is noisy, turn it off in the notification settings rather than ignoring the whole stream.

When to react​

Open the notification right away when it is connected to:

  • a task where you own the result;
  • a mention in a comment;
  • a deal or inquiry assigned to you;
  • a due date, status, assignee, or priority change;
  • work returned for rework;
  • a request to accept a result or check a file;
  • an automation action that changed a task, participant, or due date.

If the notification only informs you about an event, first decide whether action is needed. Not every notification needs a reply, but important notifications should lead to a clear next step.

How to read a notification​

  1. Open the notification and go to the related object.
  2. Check the latest comment, status, due date, and assignee.
  3. If action is needed, leave the answer in the work context, not in a private chat.
  4. If the notification is about a file, check that it opens and that the current version is clear.
  5. If the event was created by automation, check the result: status, participants, due date, comment, or related task.
  6. If no action is needed, mark the notification as read after checking the context.

Do not clear notifications mechanically. For a manager, this risks missing acceptance, a blocker, an overdue task, or a responsibility change. For an employee, it risks missing a question that blocks execution.

What to Leave in Notifications​

After checking a notification, decide where the work trace should stay:

  • a short reaction or confirmation can be sent from the notification if the context is obvious;
  • a decision, due date change reason, rework request, or result acceptance should be written in the source card;
  • a file should be checked in the card or document where the version and owner are visible;
  • a disputed question should move to a task, CRM, or document comment so every participant sees it;
  • mark a notification as read only after the next step is clear.

This keeps notifications as an attention inbox, not as a separate place for decisions.

How to reduce noise​

When there are too many notifications, the problem is often not the feed itself but roles and process rules.

Check whether:

  • observers were added "for visibility";
  • all participants are mentioned without a reason;
  • automation rules create extra comments and notifications;
  • events are duplicated in private chats and tasks;
  • you are subscribed to processes where you do not make decisions;
  • whether extra delivery channels (desktop, push) are on for background events.

A good notification flow shows not everything that happened, but where a person needs to pay attention. In LadVen OS this is especially important for tasks: extra noise reduces reaction to real blockers, acceptance, and due date changes.

Last updated on