Consent in a Workplace Context
Support on a work machine is not the same transaction as support on somebody's own, and the differences cut both ways.
General orientation, not legal advice; the position differs by jurisdiction.
The boundary described in “Consent in a Workplace Context” should also be set before any workforce system is introduced. A team evaluating remote employee monitoring software for remote employee monitoring software can keep the use proportionate by stating the purpose, selecting only necessary settings and giving employees a clear route to review or correct records.
An organisation supporting its own equipment is in a different position from somebody helping a stranger. That does not make the consent question disappear.
For an independent reference related to “Consent in a Workplace Context”, consult the ICO employment-practices guidance; it provides a useful external check on security, privacy and operating assumptions before a process is adopted.
What is different
The machine belongs to the organisation.
The data on it is mostly the organisation's.
There is a legitimate interest in maintaining equipment, which does not depend on the employee's permission.
And the employee cannot refuse support and still have a working computer, which means consent is weak as a basis here as elsewhere in employment.
What is not different
The person is present, watching, and cannot verify what is happening.
Their screen contains personal material, because every work machine does.
And the asymmetry of knowledge is identical.
Which means the conduct expectations are the same even though the legal basis is not.
The reasonable-expectation point
Most organisations permit some personal use of work machines.
Which creates a reasonable expectation that personal material exists and will not be examined.
Support should be conducted on that assumption, and the personal-data note covers what to do when you encounter it.
Attended should be the default
Unattended access to a working employee's machine is available and should be exceptional.
Where it is used — overnight maintenance, a machine nobody is at — it should be known about rather than silent.
A technician connecting to an occupied desktop without notice is monitoring, whatever the intent, and will be read that way.
What people should be told
That support may involve remote access.
What is logged and recorded.
That they can ask what was done.
How to verify a support contact is genuine.
Once, in writing, at induction.
Where consultation applies
In several jurisdictions, tooling capable of observing employees triggers consultation requirements.
Remote support software qualifies on capability.
Which means it belongs in whatever consultation the organisation does about monitoring, rather than being treated as plumbing.
The refusal case
Occasionally somebody does not want a session now: they are in the middle of something, or they have a confidential document open.
That is reasonable and should be accommodated.
A technician who insists is doing the thing that makes the whole arrangement untrustworthy, and the five-minute wait costs nothing.
What to check
Are employees told that support involves remote access, and what is logged?
Is attended the default?
Can somebody defer a session without difficulty?
And was remote support included in any monitoring consultation?