An observer in Bitrix24 (Alaio) is someone who follows a task or a deal without working on it: they get notifications and read comments, but don't move deadlines or stages. The role is indispensable for managers and adjacent teams, yet it comes with two chronic irritations: observers are forgotten where they're needed, and forgotten again where they're no longer needed — and the notification feed turns into noise. Let's sort out the roles one by one and — most importantly — how to manage observers automatically.
Roles in a task: who is who
A task has four roles. Created by is the person who sets the task and accepts the result — only they can finally complete the task if review is enabled. The responsible person does the work; there is always exactly one. Participants work alongside the responsible person: they have the same rights to change the status, and the task lands in their "Doing" list. Observers see the task, comment on it and get notifications — but change neither the deadline nor the status, and the task doesn't count toward their workload. The practical distinction is simple: a participant "also does the work", an observer "stays in the loop". A typical mistake is adding a manager as a participant "so they can see it": the task clutters their to-do list; for "seeing", the observer role exists.
How to add an observer or a participant to a task
In the task form, below the responsible person, there are Participants and Observers links — pick people from the company structure, both when creating the task and later. In the creation form the block may be collapsed — expand it with the More button. An observer can add themselves by opening someone else's task. The built-in limitation: you can't bulk-add or bulk-remove an observer across a hundred tasks — only open them one by one. That's exactly a job for automation: the Update task by ID robot changes any task fields from a workflow; observers and participants are passed in JSON as the AUDITORS and ACCOMPLICES fields — lists of employee IDs. Combined with robots in tasks, this gives you a rule like "task is overdue — add the department head as an observer".
Observers in deals, leads and smart processes
In CRM, the observer is a separate field on the card: deals, leads, contacts, companies and smart process items. An observer sees the card even if role permissions hide other people's deals from them, and gets notifications about its events — a handy way to grant targeted access without reshuffling permissions. They're added in the card next to the responsible person. The weak spot is the same as in tasks: everything is manual. Forget to add the manager to a key deal — they learn about the problem at the weekly meeting; dismiss an employee — they linger as an observer on hundreds of cards.
Automatic observer management in CRM
The Manage observers robot takes over the manual routine: in a workflow or among stage automation rules, it adds, removes or fully replaces the list of observers on the current deal, lead, contact, company or smart process item. Three modes cover the typical scenarios. Add: a deal crosses the million mark — the head of sales becomes an observer automatically; a customer with strategic status — the account director is added as an observer. Remove: the deal is closed — the observers are taken off, and the feed stops buzzing for them. Replace: when a customer is handed over to another department, the old observer list is swapped for the new one wholesale. A condition on the amount, the stage or a card field decides who gets looped in and when — the rule works identically on every deal, with no reliance on human memory.
Frequently asked questions
How is an observer different from a participant? A participant takes part in the work: changes the status, reports, has the task on their list; an observer only watches and comments. Can an observer remove themselves from a task? Yes — "leave observers" is available to the observer right in the task form. How do I mute the notification noise while staying an observer? Point-by-point — unsubscribe from the notifications of a specific task; if you don't need the notifications at all, it's cleaner to leave the observers. Does an observer see a deal that permissions hide from them? Yes, observing grants access to that specific card — which is exactly how you avoid widening role permissions for a single case.
Conclusion
An observer "stays in the loop", a participant "also does the work"; mixing them up breeds noise and bloated to-do lists. Roles are set by hand in the cards, while everything bulk and conditional — "add the manager to high-value deals", "remove observers after closing", "take the dismissed employee off the tasks" — is done by the Manage observers and Update task by ID robots from the Roboteka catalog. Free to install from Bitrix24 Market; if the scenario you need isn't there, describe the task and we'll build the robot for free.