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

Search and Event Feed

Search and the event feed help you return to work context quickly: find an object, open a card, review recent changes, and run an available action without browsing every module.

Use the feed as the portal work journal. It shows what changed, who may need to react, and where the event came from.

Where to Find It

Global search is available in the portal top bar. It can find accessible tasks, chats, CRM records, documents, mailbox messages, and workflow tasks.

The event feed is available at Feed (/feed). It displays event cards from tasks, CRM, chats, documents, mailbox, workflows, and other work areas.

Use global search when you know a title, participant, customer, email, or text fragment. Results follow your access rights: objects you cannot access should not appear.

Some results include quick actions such as open, reply in chat, mark as read, complete a workflow task, or jump to a related screen. Check the object before acting, especially when names are similar.

If mailbox results are temporarily incomplete, the portal can show that the mail index is updating. Search again later or open the mailbox directly.

Event Feed

The feed groups events into cards so you can track work without switching modules. A card usually shows source, event type, short description, actor, time, unread state, and available actions.

Use it to see new comments, assignments, status changes, attention items, source records, and confirmations that an important change was saved.

Filters and Search Modes

Filter the feed by work domain, event group, unread state, priority, and text. Advanced search modes help in different cases:

  • keyword for exact fragments;
  • semantic when you remember the meaning;
  • hybrid for normal work checks.

If the feed is noisy, filter unread events or one domain first. Do not disable important notifications when filters solve the problem.

Good Practice

  • Use global search for fast navigation and the feed for recent-event control.
  • Check the event domain before acting.
  • Start the day with unread and high-priority events.
  • Open the source card for disputed changes.
  • If an object is missing, check access rights, archive state, and query wording.