> ## 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.

# Device sync

> Sync devices from Jamf Pro, Fleet, Iru, Microsoft Intune, or Omnissa into Assets on a schedule, matched to the people who hold them.

Device management integrations sync their devices into Assets on a schedule. Each device is linked to the Ravenna user whose email matches the device's user in the source system, so you always know who holds what. Devices without a matching user sync unassigned.

## Type naming

| Integration | Type name pattern | Interval |
| - | - | - |
| Jamf Pro | `Jamf <platform>` for computers, `Jamf <device type in lowercase>` for mobile devices | 12h |
| Fleet | `Fleet <raw platform>` (Linux often reports the distribution), or `Fleet Other` | 6h |
| Iru | `Iru <platform>`, or `Iru Other` | 6h |
| Microsoft Intune | `Intune <operating system>`, or `Intune Other` | 12h |
| Omnissa | `Omnissa <platform>`, or `Omnissa Other`. Only Enrolled devices sync. | 12h |

***

## Constraints and gotchas

* Only these five integrations sync into Assets. JumpCloud and other device sources show devices on ticket cards and in lookups but do not create assets.
* Asset sync is off by default for every device integration. An org admin adds Asset under Sync scopes in the connection's Configure settings; until then, connecting syncs nothing.
* Flags: Sync scopes needs `integration-sync-capability-toggle` (on by default). Configure Asset Mapping needs `ASSET_FIELD_MAPPING` (off by default), and once a mapping is saved only mapped fields sync.
* Sync intervals are fixed per integration and are not configurable.
* Synced types start with no linked workspaces, so a freshly connected integration shows nothing in any workspace's Assets tab until an admin links the types.
* Each sync rewrites name, description, type, and fields on every synced asset. Manual edits and type renames are overwritten.
* 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.
* A sync removes types it no longer produces, so saved views, filters, or workflow conditions pointing at an old type need updating.
* Jamf syncs computers with Read Computers and mobile devices with Read Mobile Devices. With only one privilege, the other kind is skipped, its existing assets are kept, and the run shows Completed with errors.


## Related topics

- [Agent tools](https://docs.ravenna.ai/integrations/intune/agent-tools.md)
- [Workflows](https://docs.ravenna.ai/integrations/intune/workflows.md)
- [Device lifecycle](https://docs.ravenna.ai/guides/playbooks/it/device-lifecycle.md)
- [Overview](https://docs.ravenna.ai/integrations/jumpcloud/overview.md)
- [Setup](https://docs.ravenna.ai/integrations/jamf/setup.md)


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