Remote screen access (beta)

Remote screen access lets a technician view the endpoint desktop. Capture is implemented per platform on Windows, macOS and Linux, and sessions are bound to an authorised operator in the same way terminal sessions are.

This capability is offered as beta, and the label is doing real work rather than hedging. Two things are not finished: multi-monitor handling, and the end-user consent flow. If you rely on either — and any organisation supporting desk users with multiple displays relies on the first, while any organisation with a works council or a strict privacy posture relies on the second — evaluate carefully before building a process on top of it.

On macOS, screen access requires the Screen Recording privacy permission to be granted to the agent. This is an operating-system control, not a product setting, and without it the session produces nothing useful. If you deploy through a device-management platform, pre-approve the permission in a configuration profile so users are not asked to make the decision themselves.

Screen access is the right tool for a narrow set of problems: things that are visual, things where the user cannot describe what they are seeing, and things where the fault is in an application rather than in the system underneath it. For everything else the remote terminal is faster and less intrusive.

Use it with the user's knowledge. Until the consent flow is complete, that obligation sits with your process rather than with the product, and in several jurisdictions it is a legal obligation rather than a courtesy. Set a policy, tell your technicians what it is, and make it visible to the people whose desktops are in scope.