Presence exposure is itself a surveillance risk
Aliases: online status surveillance · presence dual use · availability monitoring
What it is
The online and activity status exposed for collaboration doubles as a behavioral record anyone can repurpose: whether I am here, when, for how long, and how fast I respond. This is not an edge case of presence being "misused" — it is an intrinsic property. The same awareness data serves collaboration and evaluation alike, a general mechanism established in the discussion of awareness data versus surveillance. What this leaf covers is the presence-specific expression: how an always-on green dot changes user behavior, and which guardrails presence exposure needs beyond what general dual-use analysis already supplies.
Why it happens
Presence exposure cuts deeper than other awareness layers because of its continuity and granularity. Online status is not a one-time disclosure but a standing broadcast: while logged in, my login times, absences, late-night activity, and vanishing lunch breaks all accumulate into a visible time series. The moment that series is used for judgment — "why were you offline at 3pm," "your average online hours ran two short last week" — the user's model of the green dot flips from coordination cue to attendance monitor, and behavior follows: idling to stay green, alarm-scheduled logins, never daring to sign off on weekends. The flip is one-way: once anyone in the team has cited online data to judge someone, everyone permanently manages the presence layer as surveillance data, and its collaborative value zeroes out at the same time. Online time is also only weakly correlated with actual contribution, so using it to evaluate output fails on methodological grounds as well.
Where it stops holding
The damage depends on who can see it, at what granularity, and whether what they see carries consequences. Peers glancing at each other's status is acceptable social signaling in most cultures; aggregation rolled up to managers, persisted into reports, or tied to performance reviews changes the nature entirely. The work itself shifts the boundary too: on-call and front-line roles carry an explicit duty to be reachable, so presence exposure is part of the job; in knowledge work "online hours" carries almost no duty semantics, leaving only the risk. In distributed teams, "online at midnight" may be nothing but a timezone offset misread as exceptional diligence — or abnormal hours.
Applying it
- Make online status visible to peers by default; configure visibility to managerial roles separately, and offer no per-person aggregated online-hours report — what needs cutting is not the green dot but its statistical form.
- Let users go invisible for the whole presence layer (shown as offline, with no functional penalty), without disclosing to others that they are invisible.
- Put in writing that presence data is not for performance evaluation, and give users transparency at the level of "who has viewed my status."
- Verification: audit the tool for per-person online-hours views or exports; sample-interview users for "staying online just to look online." A single instance means the guardrail has failed and the presence layer has tipped into surveillance.