Separate people and sessions on shared devices
Prevent ambiguous identity and accidental cross-person attribution.
Require an unambiguous link between the contributor and the recorded session. When a shared device cannot provide that link reliably, use a different authorized recording method.
Separate device identity from contributor identity
One workstation can be used by several people, and one person can use several devices. A device label is therefore not sufficient as a person identifier. Map the contributor ID, account and session boundaries required for your report. Do not share an administrator login as a shortcut; it can blur both attribution and access control.
Try a two-person handover with fictional records
Have one authorized test user finish a short fictional task and sign out using the approved process. Have a second test user start another task. Inspect each user’s view and the permitted reviewer’s export. Verify that neither session appears under the wrong person and that earlier details are not exposed improperly. Record a fail if the system cannot explain the handover.
Check the exported identity, not only the screen
A display name may be repeated or changed. Confirm that the recipient receives a stable identifier or a controlled mapping. Time Doctor’s export documentation describes optional employee identifiers; exact availability and mapping still need verification in the selected workflow. Do not merge records solely because the workstation or displayed name matches.
Provide a fallback when identity is uncertain
If the handover cannot be established, preserve the original record and request clarification rather than assigning the time to whoever is currently logged in. A manual entry with a reviewed contributor statement may be more appropriate than ambiguous automatic capture. Before removing an account, preserve the information needed to interpret its historical records and transfer unresolved work to a named reviewer.
Continue this work-record check
Use the linked guide for the next decision in this workflow. Keep your original records separate from experiments and record any unresolved requirement before changing a live process.
Sources and boundaries
Primary documentation supports the dated product facts. Proposed checks and fictional examples are our editorial method, not observed product results.
- DeskTime — roles · checked September 23, 2026
- Time Doctor — export · checked September 23, 2026