---
title: "Remote access"
description: "Connect to a managed endpoint, with the consent, the audit trail and the limits your policy sets."
url: "https://support.outpostplatform.com/guides/remote-access/"
product: "depot"
type: "how-to"
status: "stub"
ai_summary: "Guide to remote access in Outpost. A technician opens a session to a managed endpoint through Depot; the mode is resolved between what the endpoint supports and what policy allows rather than chosen by the technician, and every session is consented to and recorded."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/guides/remote-access.md"
license: "CC BY 4.0"
---

# Remote access

Remote access is the feature people judge a management platform by, and the one
with the most ways to get consent and auditing wrong. In Outpost a session is
opened through Depot, the mode is resolved rather than picked, and what a
technician can do is set by policy on the endpoint rather than by the technician.
This guide is for support staff and whoever writes that policy.

<!-- TODO: write this page against the how-to template.

Sections:

- Before you begin: the remote access permissions, and an endpoint whose
  policy allows it.
- Start a session from the endpoint view.
- Consent: what the person at the machine is asked, and when they are not.
- How the mode is resolved between the endpoint and the policy, and why it is
  not a dropdown.
- What a session can and cannot do, and how to narrow it.
- Unattended access, and the extra conditions on it.
- Recording and the audit trail: what is kept and for how long.
- Turning remote access off entirely for a client or a group.
- If something goes wrong: no session offered, a session that will not
  connect, and poor performance on a slow link.
-->

Follow the [how-to template](https://gitlab.com/outpostplatform/docs/-/blob/main/templates/how-to.md).