What does the business-customer LCP manage, and which business event triggers each of its operations?
It creates, changes and deletes company customers in the CRM and propagates them to the IdP; the triggers are a signed contract (create), a change notice from the customer (update) and the customer ending the business relationship (delete), always carried out by sales staff.
| Operation | Trigger | In the CRM | Propagated to the IdP |
|---|---|---|---|
| Create | Contract signed | Sales records the Customer with e-mail and company | Find the user by e-mail; create it if absent, otherwise just add the company |
| Update | Customer reports a change | Sales changes the customer data | Company updated; if the e-mail changed, find the user by the old e-mail, then set the new one |
| Delete | Customer ends the relationship | Sales deletes the Customer | The user is deleted completely, with all attributes |
Two design ideas are worth noticing. First, business events drive the process, not IT events: nothing happens in the IdP until something happens in the business (a contract, a request), and the CRM is the place where that event is recorded. Second, the IdP is never edited by hand for business data: the CRM is the leading system for business customers, and a synchronisation carries its changes over. That makes the CRM the single place to look when someone asks "why does this user have that company?", especially since the model assumes the CRM keeps a change history.
Go deeper:
User provisioning software (Wikipedia) — how changes in a leading system are pushed out to accounts in target systems.- Single source of truth (Wikipedia) — why every data element should be mastered in exactly one place.