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 them as the portal work journal. Search is for fast navigation, while the feed shows what changed, who may need to react, and where the event came from.

Where to Find It

Global search opens from the portal top bar. It searches objects available to the user and can return tasks, chats, CRM records, documents, mailbox messages, workflow tasks, and other work records.

The event feed is available at Feed (/feed). It shows event cards from tasks, CRM, chats, documents, mailbox, workflows, telephony, site forms, Telegram, WhatsApp, and reminders.

Results depend on access rights. If a person cannot access an object, it should not appear in search or in the feed.

When to Use Search

Use global search when you need to jump to a known object:

1. Find a task by title, client, participant, or description fragment.
2. Open a chat or message when you remember part of the text.
3. Find a CRM card by client, opportunity, contact, or email.
4. Return to a document, email, or workflow step.
5. Check where in the portal an event mentioned by a colleague lives.

Results may be grouped by object. If several records look similar, check the domain, title, preview, and match highlight before opening a card.

Quick Actions from Search

Some results include actions directly in the search popup: open, reply in chat, mark a notification as read, set a task in progress, complete a task, or complete a workflow step.

Use quick actions only for clear cases. If the result is tied to a customer, document, deadline, or disputed change, open the card first and review the context.

If an action is unavailable, it usually means missing permissions, a changed object state, or an action that no longer fits the current state. Open the source and continue there.

When to Use the Feed

The feed is not for finding one known object; it is for controlling the work stream. It helps you:

• see new comments, assignments, reactions, and status changes;
• find events that need attention;
• review unread events for the day;
• open the source task, CRM card, chat, document, email, or workflow;
• confirm that an important change was recorded;
• reply quickly in a task, CRM card, or chat when the action is available.

For managers, the feed is a risk and delay overview. For contributors, it is a list of new signals that need a response.

Daily Event Triage

Use the feed as a short work review, not as an endless news wall:

1. Open unread events and mentions.
2. Check events with deadlines, clients, documents, and blockers first.
3. For each event, choose the next action: reply, open the source, hand it to the owner, postpone it, or mark it as read.
4. If the event affects a decision, deadline, or acceptance, open the source card and leave the comment there.
5. At the end, leave only events that still need a next step.

This routine does not replace work in tasks, CRM, or documents. It helps you keep the signal and move to the right module with context.

What an Event Card Shows

A feed card usually includes:

• event domain: tasks, CRM, chat, mailbox, documents, workflows, telephony, site forms, Telegram, WhatsApp, or reminders;
• event type: communication, state change, or attention event;
• source object title;
• short description or message preview;
• actor or participant;
• event time;
• card, event, and unread counters;
• high-priority, overdue, mention, or checklist markers;
• available actions.

If a card contains several events for one object, expand the latest events or open the source card. Do not make a decision from a short preview when the situation affects a deadline, customer, or document.

Filters

Use filters to reduce noise:

• domain chips: Core (including reminders), tasks, CRM, chat, workflows, telephony, mailbox, documents, Telegram, WhatsApp, and site forms;
• event group: communication, state change, task detail, needs attention, or timer;
• unread only;
• priority;
• event text;
• sorting by date or relevance.

This feed has no dedicated Disk or Extranet chips. Do not treat those areas as separate feed filters; use global search or open the source module when you need to find a Disk or Extranet object precisely.

The feed groups events for the same object into one card. Grouping can hide some events; a separate hidden-events counter shows when that happens. The first page contains up to 20 cards and more pages load as you scroll. Summary counters use a separate sample of up to 200 events, so they can be higher than the number of visible cards.

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

Feed Search Modes

Advanced filters let you choose the search mode:

• keyword - for an exact text fragment;
• semantic - when you remember the meaning but not the exact words;
• hybrid - the normal work mode that considers both words and meaning.

For operational review, start with hybrid mode. If you need an exact phrase from an email, comment, or document, switch to keyword mode.

Replies and Inline Actions

Some cards let you answer directly from the feed: in a chat, task comment, or CRM comment. These replies are useful for a short confirmation or clarification.

Do not use a short inline reply for a complex decision. If you need to attach files, review history, change a deadline, accept work, or approve a document, open the source object.

Managing Object Notifications

When one object creates too much feed noise, use Mute notifications (mute_object). This hides or marks that object's cards in the feed; it does not delete the source task, CRM card, chat, or document. Unmute notifications (unmute_object) restores its events. If the card does not change after the action, notifications are not considered muted: retry and verify the result.

Unread Events

Unread means the portal considers the event relevant to your attention. Do not mark everything as read mechanically.

A practical order:

1. Filter unread events.
2. Review high-priority events and mentions first.
3. Open disputed cards in their source.
4. Reply or run the action.
5. Mark the event read only after that.

If Nothing Is Found

If search or the feed does not show the expected object:

• check access rights and membership in the project, department, or CRM context;
• make sure the object is not archived or deleted;
• shorten the query to key words;
• try another search mode;
• open the source module directly: tasks, CRM, mailbox, documents, or chat;
• if mailbox results are incomplete, wait for the mail index to refresh and search again.

Do not create a duplicate task, customer, or document just because the first query found nothing. Check rights and wording first.

Safe Screenshots

Use only a documentation demo workspace for search and feed screenshots:

• training tasks, customers, documents, emails, and chats;
• neutral employee and customer names;
• no real emails, phones, links, call recordings, attachments, or personal data;
• no private project, document, or deal names;
• no raw technical codes, internal links, or mixed languages;
• interface in the selected language.

Global search and feed screenshots are especially sensitive because they aggregate data from many modules at once. One dirty result makes the whole frame unsuitable for publication.

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.
• Do not mark an event as read until the next step is clear.
• For repeated noisy events, tune filters and notifications instead of ignoring the whole feed.
• If an object is missing, check access rights, archive state, and query wording.

Related Scenarios

• Tasks
• CRM
• Mailbox
• Documents
• Workflows
• Notifications