Clerical staff can propose resident merges, stewards must approve them, and only then does the MDM system execute the merge. What does this workflow emphasize?
Select an answer to reveal the explanation.
Short Explanation
One person spots the possible twin, another person says 'yes that is really the same resident,' and the system does the glue work—three beats, not one free-for-all. That is segregation of duties for merges. Speed without gates is how false positives sneak in.
Full Explanation
Controlled merge workflows separate proposal, approval, and execution so high-impact identity changes receive appropriate review. Clerical users surface candidates; stewards apply domain judgment; the platform executes under audit. Collapsing those duties into unchecked auto-execution or bypassing stewardship increases false-positive harm and weakens accountability.