---
key: set-service-asset-defaults
title: Set service asset defaults
audience: staff
section: settings
routes: ["/settings/org/service-assets/defaults"]
permissions: ["crm.service_assets.admin.manage"]
features: ["crm.service_assets"]
since: 0.0.1
updated: 0.0.1
status: published
summary: Decide whether every asset needs a subtype, whether technicians can add new types and statuses on the spot, and what happens when a captured asset does not match your list.
keywords: [asset rules, require subtype, inline create, capture, equipment defaults, asset editor, tech can add]
related: [set-up-service-asset-types-and-subtypes, choose-a-profile-for-each-service-asset-type, set-up-service-asset-statuses-and-lifecycle-states]
---

In the sidebar, open **Settings**, then choose **Service Asset Defaults** under **Accounts**. The page address is `/settings/org/service-assets/defaults`. It is the **Defaults** tab of the service asset settings.

The page is a list of switches. Each one saves the moment you flip it and confirms with a message. All of them start on except **Require subtype on assets**.

## Before you start

- Your role needs permission to manage service asset settings. Otherwise the page says so and shows nothing else.

## Steps

1. Switch on **Require subtype on assets** if an asset must always have a subtype under its type. Leave it off while your subtype list is still thin.
2. Leave **Auto-apply profile from type** on so picking a type in the asset editor also sets the profile chosen for that type.
3. Decide how much your team can add on the fly. **Allow inline type creation** and **Allow inline subtype creation** let people whose role can manage service asset settings add types and subtypes from the asset editor; **Allow inline status creation** and **Allow inline lifecycle state creation** do the same from the status and lifecycle pickers; **Allow inline identifier type creation** lets them add identifier types from the editor.
4. Leave **Stage invalid capture taxonomy** on so that equipment sent in with a booking, a form or a work order line, whose type is not on your list, is kept with that record instead of creating an asset. With it off, the mismatch is refused with an error.

## What you see

- Each row shows the rule's name, a one-line explanation and its switch.
- A message confirms each change. While one change is saving, the other switches wait.

## If something looks different

- The switches do not move: another change is still saving. Wait a moment and try again.
- A change shows an error: it was not saved. Flip it again, and contact support if it keeps failing.
- Inline creation is on but a technician still cannot add a type: their role also needs permission to manage service asset settings.

[[route:/settings/org/service-assets/defaults|Open Service Asset Defaults]]