The customer relationships guide tells the story with screenshots. This page is for the mechanics: who does what, exactly where the system says no, and what gets written down. Every diagram describes what actually happens — including the refusal branches, which are the paths people otherwise discover in production.
Conversion is one action that creates three records — account, contact and deal — and it does not reverse. Note that the lead is not deleted: it is the only thing that can answer where a deal originally came from.
Two things here are not decoration: every stage move is written down with who and when, and a deal that stops moving raises a task by itself. Follow the amount branch — somebody without the permission sees "withheld", not zero.
The separation-of-duties branch is the point: the person who requested the discount cannot approve it, even holding both permissions. Note also that a price below the floor is refused before any approval is opened at all.
The clock counts real working hours — a Sunday-to-Thursday week with public holidays out — so a complaint arriving on Thursday afternoon stops the clock until Sunday. Escalation happens before the promise breaks, not after.
This is the answer to the documented reason CRM projects fail: nobody types anything in. Note what is not stored — the message body stays in mail, and only the subject, a snippet and a reference are kept here.
No password and no sign-up. Critically, a portal login creates no tenant membership — it consumes no paid seat, and its token is refused by every back-office screen.