Private conversations follow current participants
Replacement owners, providers and rebound accounts no longer inherit earlier private messages. Maintenance access follows the exact tenant contract, including private files and notices.
- Improvements and fixes
Message audience and attribution: New private messages capture current recipient identities and parent context. Conversations, inbox notices and email preparation use the same current checks. Original author attribution is captured instead of inferred from later account edits. Current company scope retains history; legacy messages without recipient evidence show a red Accountant marker and are not automatically shared with replacement parties.
- Improvements and fixes
Exact maintenance contract: Relinking a customer to another tenant in the same unit no longer grants the old maintenance job, invoices, tickets, exports or private file bytes. Existing scoped company and assigned-provider access remain separate. No financial party or historical liability is changed.
- Improvements and fixes
Final email recipient check: After claiming a queued notice, the worker rereads authority and compares the recipient and message context immediately before transport. Changed authority/address/context suppresses stale mail; a failed current read holds it without sending or claiming delivery. Provider setup and sending policies remain unchanged.
No production conversation is migrated, shared or sent by deployment. Legacy context requires authorised company review and explicit relevant communication. Populated ownership/message paths are tested with isolated synthetic records; independent native role acceptance remains separate. Already accepted external sends cannot be recalled by a later access check.