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

# Assets

> Org asset inventory, source bindings, and operational context for tickets and access.

**Assets** gives operators and automations reconciled inventory: laptops, mobile devices, licensed software, and related assignments. Data is org-scoped. The hub is not tied to a single team's ticket queue.

Assets support the following:

* Faster incident triage ("which device does this user have?")
* Access decisions grounded in entitlement and device posture
* Automation steps that look up or update asset records

Inventory syncs from connected providers (Microsoft Intune, Google Workspace, …). See [Assets integrations](/integrations/assets/overview).

## Find an asset

<Steps>
  <Step title="Open Assets.">
    Open **Assets** from the sidebar.
  </Step>

  <Step title="Search or filter.">
    Search or filter the table by type, owner, status, or source.
  </Step>

  <Step title="Open asset detail.">
    Select a row to open **asset detail**.
  </Step>
</Steps>

## Asset details

The detail page is organized into sections:

| Section | Content |
| - | - |
| **Header fields** | Type, assigned to, assignment source, and state |
| **Software / Hardware / Ownership & lifecycle / Other** | Provider fields grouped by category |
| **Related conversations** | Conversations linked to this asset |
| **Sources** | Which sync source contributed the record, shown in the side panel |
| **Recent activity** | Recent changes, with an option to view full history |

Use **Reassign** when ownership changes. Add comments through the composer when your process requires an audit trail on the asset.

## Manage asset sources as an admin

<Steps>
  <Step title="Connect a provider.">
    Connect Intune or Google Workspace: [Integrations](/integrations/assets/microsoft-intune).
  </Step>

  <Step title="Open the Assets tab.">
    Open the connection under **Integrations** and select the **Assets** tab.
  </Step>

  <Step title="Create or verify the sync source.">
    Create or verify an org-level sync source.
  </Step>

  <Step title="Run and monitor the initial sync.">
    Run initial sync and monitor run stats in the admin surface.
  </Step>

  <Step title="Schedule recurring sync.">
    Schedule recurring sync when the admin surface exposes a schedule control.
  </Step>
</Steps>

Disconnecting a source preserves historical assets while stopping new crawls.

## Asset types

Exact types depend on connected providers. Common categories:

| Type | Examples |
| - | - |
| Devices | Laptops, mobiles, ChromeOS managed devices |
| Applications | Installed or assigned software entitlements |
| Licenses | Subscription or seat assignments |

Okta contributes application inventory, not devices: see [Okta assets](/integrations/assets/okta).

## Related topics

* [Integrations: Assets](/integrations/assets/overview)
* [Access](/setup/access): entitlement-aware requests
* [Help desk](/setup/help-desk): linking operational context to conversations
* [Troubleshoot connections and sync](/setup/troubleshooting/connections-and-sync)


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