Whistleblower management

In the event form, the Participants field accepts several people at once — even in an event you haven't saved yet: the invitations go out together with the event. When you reopen the event to edit it, the list shows who was invited and each person's status. Inviting again someone who has already been invited does nothing (it doesn't resend or change the answer the person already gave).

While the person doesn't answer, the event doesn't take up their time slot and they keep appearing as free for other invitations. It's the "Your invitations" box, at the top of the screen, that waits for that answer. This is on purpose: an invitation doesn't decide anyone's schedule — the invitee decides.

When choosing participants, or when changing the time, the screen says who already has a commitment in that window. It's a WARNING, not a block: you can save even with a conflict, because being in two meetings is a real situation that only the person inviting can resolve. Two things matter so you don't trust the number too much: (1) the check looks at calendar events — yours and the invitations the person ACCEPTED — and doesn't consider demand deadlines, rituals or public scheduler slots, which are not "busy" in the meeting sense; (2) times that only touch are not a conflict: a meeting that ends at 10 a.m. and another that starts at 10 a.m. coexist.

A REQUIRED participant is someone who needs to be there for the meeting to happen; OPTIONAL is someone it would be good to have. The difference governs how the conflict warning reads: the highlighted summary counts only the required ones, and the optional ones appear on a discreet line — an optional participant's conflict doesn't prevent the meeting. That's what keeps the alert useful; if it mixed the two, it would become noise and you'd stop reading it. Details that avoid surprises: marking the same person in both lists makes REQUIRED prevail; moving someone from one list to the other changes only the role and preserves the answer they already gave (a "declined" stays declined); and removing someone from the list removes their invitation, so as not to keep asking for an answer about a meeting that is no longer theirs. Invitations created before this version come in as required, which was the meaning they had.

Porque convite só ocupa a agenda depois de ACEITO — até lá aparece como pendente para quem foi convidado. O aviso de conflito ajuda a escolher o horário, mas não impede salvar. Camadas (sua, time, visitas, entregas) têm dono e visibilidade próprios.

The calendar always answers: “Event removed from the calendar” with its title, or “Nothing was removed” when the event had already left or comes from another screen (a ticket meeting, a bill due date). Those mirrored events are removed on the screen they come from.