Permissions And Trust

How to revoke access or end a session

A trustworthy remote-control flow needs visible end-session behavior and clear account, app, device, and OS revocation paths.

Direct answer

To end a Remote Comp session, close the active session path from the host or controller and confirm the host is no longer being controlled. To revoke access, use the product account path, app state, device pairing controls, and OS permission settings that apply to the setup.

Steps

1

End the active session

Close the current control path and verify the host is no longer being controlled before moving to broader revocation.

Revocation checklist showing session end, account, device, app, and OS permission paths.
Revocation should cover the session, account, app, device, and OS permission surfaces.
2

Remove pairing or account access

Use the product account or pairing path when it exists. Record who made the change if the action affects a team workflow.

Revocation checklist showing session end, account, device, app, and OS permission paths.
Revocation should cover the session, account, app, device, and OS permission surfaces.
3

Review OS-level permissions

Use macOS privacy settings to review Screen Recording, Accessibility, microphone, camera, or Local Network permissions that were granted.

Revocation checklist showing session end, account, device, app, and OS permission paths.
Revocation should cover the session, account, app, device, and OS permission surfaces.

FAQ

Can copy promise one-click revoke?

Only if product evidence proves that exact behavior across the relevant access surfaces.

Should support leave sessions running?

No. Support sessions should be the shortest session that resolves the authorized issue.

Did this help?

Review support guardrails
Open