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

> Create asset types, choose their fields and sections, and link them to the workspaces that should see their assets.

An asset type defines a kind of asset, such as **Laptops**, **Monitors**, or **Software Licenses**. Each type has a name, icon, color, and description, a set of fields, and a list of linked workspaces that decides who sees its assets.

## Asset type model

| Property | Detail |
| - | - |
| Name | Unique per organization, case-insensitive |
| Icon and color | Lucide icon name and a color |
| Workspaces | Zero or more linked workspaces. Controls which workspaces show the type's assets. |
| Fields | Shared field definitions arranged in up to 20 sections. Status is built in and always first. |

***

## Constraints and gotchas

* Field definitions are organization-wide. A label match when adding a field reuses the existing definition.
* Assignees can be single select per asset type (Assignees row menu > Make single select). On a single-select type, any assignment, including bulk, workflow, and agent assignments, replaces the current holder. The last pick in a batch wins.
* Deleting a field removes it from every asset type.
* Deleting an asset type moves its assets to another type or to Uncategorized.
* Field inheritance: an asset type's layout is its own sections plus one section per ancestor (titled with the ancestor's name) holding ancestor fields not already placed. Values can be set on inherited fields. Saving an inherited section on the child type is rejected; edit it on the ancestor.
* Asset types can have multiple parents. Extend (admins) sets them, and in tree view admins can also drag to reparent. The Extend dialog disables descendants (Cannot select a descendant) and existing ancestors (Already inherited). Tree view counts and lists include descendant types; flat view shows each type on its own.
* Asset types created by device sync have no linked workspaces, and sync rewrites their names on every run, so renaming a synced type does not stick.
* Creating a type from a workspace's Assets tab links it to that workspace. CSV import links the types in the file to the workspace it ran from.


## Related topics

- [Assets](https://docs.ravenna.ai/documentation/platform/assets/overview.md)
- [Delete an asset type](https://docs.ravenna.ai/api/asset-types/delete-an-asset-type.md)
- [List asset types](https://docs.ravenna.ai/api/asset-types/list-asset-types.md)
- [Create an asset type](https://docs.ravenna.ai/api/asset-types/create-an-asset-type.md)
- [Update an asset type](https://docs.ravenna.ai/api/asset-types/update-an-asset-type.md)


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