Run a Remote Support Session on a Rented Mac

Published November 11, 2026 • Figment editorial team

Supporting someone on their rented Mac does not have to mean grabbing the wheel. macOS Screen Sharing has a distinct observe mode: you see what the user sees, a click-and-hold produces a visible highlight they can follow, and your pointer cannot move their mouse or open files until they explicitly grant control. Using control mode without asking is jarring and hard to undo — start in observe and escalate on request.

Direct recommendation. For one-off support, built-in macOS Screen Sharing as described in Apple's Share the screen of another Mac is enough. For recurring team support, Apple Remote Desktop adds a multi-client observe window and per-client mode toggles. On the Figment side, if the user is on an M-series rental and you want packaged monthly support attached to it, the Managed Build Mac plan ($249/month: one M-series Mac, CI setup, backups, monitoring, 30 minutes monthly support) is the practical entry point — request a quote to agree the support scope before purchase.

One caveat before you start: this guide assumes the user is on a Mac they can reach interactively — a physical M-series rental, a desktop Mac, or a laptop. Figment's $29 virtual Intel macOS environment is reached through a browser console, not VNC, so Apple's Screen Sharing flow below does not apply to that plan. For VM support, screen-share the browser tab from the user's workstation instead.

Observe Mode vs Control Mode: What Each Permits

Once connected, Screen Sharing offers two operating modes.

Observe mode. Apple's documentation states you "can watch what's happening on the shared screen, but you can't control the pointer, move windows, open and close documents, or do other tasks." If the remote Mac runs OS X 10.9 or later, you can "click and hold to highlight the screen at your pointer" — a spotlight the user sees under your cursor. The click does not interact with the UI; it just points.

Control mode. Your mouse moves the remote pointer, your keystrokes land on the remote machine, and you can open or close anything. The user watches your actions in real time.

You switch using the View menu item "Switch to Observe Mode or Request Control Mode"; the label flips based on the current mode. Start in observe, guide verbally, request control only when you need it, switch back before handing off.

Pre-Call Setup Checklist

Work through this before connecting:

Confirm the user's Mac hostname or local IP from System Settings > General > Sharing (hostname is shown under Local hostname).
Confirm Screen Sharing is turned on at System Settings > General > Sharing > Screen Sharing.
Agree the user will stay at the screen for the duration of the call.
Open a separate voice or video channel (phone, Teams, Zoom) — you will narrate while watching.
Confirm you have the VNC password or the Apple ID the user will invite.

Starting an Observe-Only Session

From the Screen Sharing app.

Open Screen Sharing via Spotlight or /System/Library/CoreServices/Applications/Screen Sharing.app.
Enter the user's address in Connect to.
Authenticate with the credentials or Apple ID invite they send you.
Once connected, open View and confirm you are in Observe Mode (the menu item reads "Request Control Mode").

From the command line (opens Screen Sharing and connects in one step):

open "vnc://username@hostname-or-ip"

Replace username and hostname-or-ip with the account and address; macOS prompts for the password. Do not paste credentials into chat or a shared terminal.

From Finder. Open a Finder window, browse Network in the sidebar, right-click the user's Mac if both machines are on the same network or VPN, and choose Share Screen.

Apple Remote Desktop (Mac App Store, paid) adds a dedicated multi-client observe window and per-client observe/control toggles; worth it for teams running regular sessions, overkill for one-offs.

Guiding Without Controlling: The Pointer Highlight

In observe mode, click and hold on the remote screen to produce a highlight circle at your cursor on the user's display. Use it as a pointer:

"Move your pointer to the top-left — I'll put a highlight on the Wi-Fi icon."
Hold the mouse button on the target. The user sees the glow.
Release, then describe the next step.

This keeps the user's hands on their own keyboard, builds their familiarity with the Mac, and avoids the disorientation of watching their cursor move on its own. Reserve control mode for multi-step tasks that are too fiddly to narrate.

Requesting Permission to Take Control Mid-Session

When you need control, ask verbally and use the system dialog:

In the active session, open View and choose Request Control Mode.
The user sees a confirmation dialog and clicks Allow or Decline.
If allowed, narrate every action: "I'm opening Terminal now" — "I'll drag this file to the Trash."
The instant the task is done, open View and switch back to Observe Mode. Do not stay in control while explaining the next step.

If the user declines, respect it. Offer to slow down, send a screenshot of what they should see, or schedule a follow-up. Never escalate to admin access to override a declined control request.

Escalating to Admin Access Only When Necessary

Unprivileged control mode will not install software, change SIP-protected settings, or run sudo commands. If the task genuinely needs admin:

Ask the user to open Terminal themselves.
Have them type the sudo command word by word as you narrate.
The user enters their own admin password — they do not read it aloud and you do not need to know it.
If you need an interactive admin shell, ask the user to create a temporary shared admin account for the call and delete it immediately after. Confirm deletion before you disconnect.

Never ask a user to email, chat, or type their account password where you can see it. If a task cannot be completed inside this protocol, switch to async: written steps with screenshots, or a short recording from an equivalent test machine.

Full Support Session Checklist

Keep this open in a second window:

Before connecting

Screen Sharing enabled at System Settings > General > Sharing
User seated at the Mac and can see the screen
Separate voice channel established
Host address and credentials in hand

On connection

Connect via Screen Sharing or ARD
View menu shows "Request Control Mode" (you are in observe)
Verbal confirmation: "I can see your screen, I'm in observe mode, I can't move your cursor"

During the session

Use click-and-hold highlights to point
Narrate each step before the user does it
Request control via View menu only when needed
Announce every action in control mode
Switch back to observe as soon as the task completes

Escalation ladder

Minor help: observe + verbal guidance
Moderate: observe → request control → narrate → back to observe
Admin: user types sudo you dictate; user enters their own password
Complex admin: temporary shared admin account, deleted at session end

Closing

Back in observe mode
User tests the fix themselves
Verbal "I'm closing Screen Sharing now — you should have full control"
Close the window
Send a written summary and any follow-up

Closing and Confirming the User Has Sole Control

Do not close your window silently. Announce the disconnect and ask the user to click or move the mouse to confirm they are back in control. If the rental is new to them, show them the Screen Sharing toggle at System Settings > General > Sharing > Screen Sharing so they can turn it off themselves when the call ends.

For ongoing support on an M-series rental, the Managed Build Mac plan at $249/month bundles one M-series Mac, CI setup, backups, monitoring, and 30 minutes of monthly support. Teams running regular sessions can look at Managed Mac Team at $999/month: two M-series Macs, two CI runners, team setup, backups, monitoring, and one hour of monthly support. Request a configuration quote to agree the macOS version, hardware delivery and support scope before you commit.