Customer case 085 · Other industries · Privacy & data control
This article is adapted from one real, anonymized domestic customer conversation. The original channel, historical offer and sales explanation are not automatically current SugarHR capabilities.
The customer’s situation and requirement
Employees used work phones that could be left at the company or held by someone else. Colleagues also knew each other's names. The customer therefore raised a real ownership problem: a number and a familiar static name did not necessarily mean the intended person controlled the access route.
Why this case needs its own decision
The risk continues after a technically correct send. Include who can unlock the phone, see old messages and inherit the address in the handover assessment instead of relying only on a name check.
A proposed approach to this requirement
The sequence below is guidance to evaluate; it is not a claim that the customer completed it.
1. Address device and inbox reassignment.
Prefer the intended person's controlled receiving channel and assess old messages before a work device or address changes hands. An originally correct send does not prevent later access by a new holder.
2. Validate identity and recipient mapping.
Inspect employee identifiers and personal addresses, including same-name people, changed contacts and unsettled leavers. Compare the preview with the approved source before the file becomes a live delivery batch.
What the conversation established—and left open
A notification issue was located, but the proposed change of channel was not shown to have been completed across the workforce.
A question to carry into the evaluation
What should we review beyond the hosting provider's name?
Review administrator scope, recipient accuracy, access responsibilities, storage and transmission arrangements, incident handling and record retrieval. Request evidence for requirements such as deployment location or certification. A cloud brand or security illustration does not establish those controls or eliminate organizational responsibilities.
Continue with relevant guidance
Browse the full case library · Requirements checklist · Compare delivery options