- Ya
- 2 Septemba 2026, 07:30 UTC
- Mwandishi
- Kamo
- Ahadi ya
- f2df460
Adding a guest to an event did not tell them, and the dialog never said so. The only thing that ever wrote to a guest was a reminder — which reaches a colleague in-app and reaches an outside address never — so inviting a client to a meeting contacted nobody, and there was no control anywhere that would have. A card under the guest list, in the shape of the privacy and reminder cards it sits between: one switch, and two route chips under it. The switch turns itself on when the first guest arrives, once and never again, because adding somebody to a meeting and having them not be told is the surprising outcome — and turning it back off has to stick even while more guests are still being added. The summary line is the part that earns the card. An outside guest has no chat thread and no Kamo calendar; email is the only route that reaches them and it is what carries the calendar file. Switching email off strands them, and nothing else in the interface would say so. Turning off the last route turns the whole thing off rather than leaving a switch that claims to be inviting people while sending nothing. Hidden for the lead callback, which owns its own save into SecurityService: mailing a lead a meeting invitation for the moment you intend to ring them is not what scheduling a callback means. "Update and notify" goes. It posted to the mail composer's own invite endpoint, which mints its own event and refuses any whose ORGANIZER_EMAIL is not the sender — a column no calendar event has ever set — and sent the guest list as it was when the dialog opened, so an edit that added somebody notified everybody except them. It could never have run in any case: it was gated on attendee.isOrganizer, which the calendar's guest sync writes as false for every row. Saving now does the job.