---
title: "Outpost Sync"
description: "Outpost Sync is a managed folder that follows a person between the machines you manage."
url: "https://support.outpostplatform.com/sync/"
product: "sync"
type: "concept"
status: "stub"
ai_summary: "Overview of Outpost Sync, the managed folder feature. A folder on a managed endpoint is kept in step with the same folder on that person's other managed endpoints through Depot, under the administrator's storage and retention rules, rather than through a consumer file sharing service."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/sync/index.md"
license: "CC BY 4.0"
---

# Outpost Sync

Outpost Sync gives somebody a folder that is the same on every machine you
manage for them, without sending their work through a consumer file sharing
service you do not control. It syncs through Depot, on your storage, under your
rules. This section is for the administrator who turns it on and decides those
rules.

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

Sections:

- What Sync is, from the point of view of somebody using the folder.
- How it works: the endpoint watches the folder, Depot holds the copy.
- Where the data actually lives, and who can read it.
- Turning it on, and why nothing runs on an endpoint until it is provisioned.
- Storage: which profiles are metered and which are not.
- Retention, and what happens to a deleted file.
- What Sync deliberately does not do.
- Limits: file sizes, counts, and what happens on a slow link.
-->

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