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

# Assets

> Track hardware, software licenses, and other resources with asset types linked to the workspaces that manage them.

Assets let you keep a record of the things your teams own and hand out: laptops, monitors, phones, software licenses, or any other resource. Each asset belongs to an **asset type**, has a **status**, and can be held by one or more people. Asset types are linked to the workspaces that manage them, so the right teams see the right assets.

> [!NOTE]
>
> Only organization admins can create, import, edit, assign, archive, or delete assets, asset types, and statuses. Workspace members and admins can view the assets in their workspace, add notes, and export an asset's activity. Everyone else can look up only the assets they hold.

Assets is in beta and available to selected organizations. To request access, contact your Ravenna representative, or reach out to the Ravenna team on Slack or through the in-app chat. Testing it? See the [beta tester guide](https://docs.ravenna.ai/documentation/platform/assets/beta).

## Overview

| Property | Detail |
| - | - |
| Scope | Organization. Asset types are linked to workspaces for visibility. |
| Access | Organization admins manage everything. Workspace members view assets of linked types, add notes, and export activity. |
| Location | Settings > Organization - Assets, and each linked workspace's Assets tab |
| Purpose | A record of hardware, licenses, and other resources, with who holds each one |

***

## Mental model

* An **asset** belongs to exactly one **asset type**. Asset types define fields and are linked to zero or more workspaces.
* Workspace visibility is by asset type, not by assignee. A workspace with no linked types has no Assets tab.
* Every read (web app, API, Copilot, MCP, ticket agent) uses one scope: organization admins read every asset, workspace members and admins read assets of types linked to the workspace, and everyone else reads only the assets they hold, of those types. An asset outside the caller's scope reads as not found.
* Asset notes are for organization admins and workspace members and admins.
* An asset has zero or more **assignees** (Ravenna users) and exactly one **status**.
* Statuses are organization-wide and each belongs to a fixed category: AVAILABLE, IN\_USE, UNAVAILABLE, RETIRED. Assignment moves status by category.
* **Retired** status takes an asset out of circulation and keeps it visible. **Archive** hides the record. **Delete** is only possible when no ticket references the asset.
* Assets come from manual entry, CSV import, or device sync from Jamf Pro, Fleet, Iru, Microsoft Intune, or Omnissa.

***

## Pages in this section

| Page | Covers |
| - | - |
| Asset types | Creating types, fields and sections, linking workspaces, deleting types |
| Statuses | Status categories, the default status, automatic status changes |
| Manage assets | Search, filters, the asset view, notes, export, bulk actions, archiving |
| Import from CSV | Spreadsheet import and its limits |
| Device sync | MDM sync behavior, type naming, per-integration notes |

Assets also appear on these pages outside the section:

| Page | Covers |
| - | - |
| Custom fields | Asset Select and Asset Type Select field types |
| Cards | The built-in Assets card |
| Workflow triggers and actions | Asset Created, Asset Updated, Asset Archived, Asset Assignment Changed, and the Create, Update, Archive, Search, and Assign Asset actions |
| MCP tools and Copilot everyday tasks | `read_assets`, `manage_asset`, `manage_asset_type`, `manage_asset_status` |
| Agent configuration | The ticket agent's Read Assets tool, scoped to what the requester may see |


## Related topics

- [Manage assets](https://docs.ravenna.ai/documentation/platform/assets/manage-assets.md)
- [Asset types](https://docs.ravenna.ai/documentation/platform/assets/asset-types.md)
- [Asset sync](https://docs.ravenna.ai/integrations/fleet/asset-sync.md)


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