> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset sync

> Sync Fleet hosts into Ravenna Assets every 6 hours, matched to the people who use them.

Fleet devices sync into Ravenna [Assets](https://docs.ravenna.ai/documentation/platform/assets/overview) on a schedule, so you always know who holds which device. Each device becomes an asset, linked to the Ravenna user whose email matches the device's user in Fleet.

## Constraints and gotchas

* Asset sync is off by default. An org admin turns it on by adding Asset under Sync scopes in the connection's Configure settings; connecting alone syncs nothing. Resync runs it immediately.
* Flag: the Sync scopes field needs `integration-sync-capability-toggle` (on by default).
* Syncs every 6 hours. The interval is fixed.
* Synced asset types start with no linked workspaces.
* Each sync rewrites name, description, type, and fields on every synced asset.
* Flag `ASSET_FIELD_MAPPING` (off by default): Configure Asset Mapping on the connection maps external fields to Ravenna asset fields. Once a mapping is saved, only mapped fields sync; with no mapping, fields are discovered by label and created automatically.
* Devices that leave the source move to a Retired-category status and keep their asset and integration link. Later syncs leave them alone. A returning device re-links to the same asset and, if still Retired, moves to In Use when held or to the default status otherwise.
* Type names use Fleet's raw lowercase platform value, and Linux hosts split by distribution.


## Related topics

- [Asset sync](https://docs.ravenna.ai/integrations/iru/asset-sync.md)
- [Device sync](https://docs.ravenna.ai/documentation/platform/assets/device-sync.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.