Asset Types
How to define the trackable assets that flow through request blocks and into procurement
Asset types define the resources that can be requested through asset request blocks in your module templates. When a collaborator submits an asset request, they are requesting a specific asset type — and that request carries all the structured information defined here into the procurement workflow.
Defining your asset types before building module templates ensures that request blocks can reference them correctly.
What an Asset Type Captures
Each asset type has a name (for internal reference), a label (shown in the UI), an icon, and a category. Beyond the basics, asset types are made useful by two additional configurations: properties and sub-assets.
Properties are custom fields attached to each request for that asset. When a collaborator requests an asset, they fill in the property values you've defined. Properties use the same response types available in question blocks — text, number, date, select, checkbox, and more — so you can capture exactly the structured information each asset type requires.
For example, a Golf Cart asset type might have a Type property with options for 4-passenger and 6-passenger, so every golf cart request captures which kind is being asked for. A Labor Call might have Call Name, Start Time, and End Time properties so that each requested call comes in with the scheduling details already attached.
Sub-Assets
Some assets are naturally composed of repeatable components. A sub-asset lets you define a nested item type that collaborators add multiple instances of beneath the parent asset.
The Labor Call example illustrates this clearly. The parent asset captures the call details — name, start time, end time. The sub-asset, called Laborer, captures the individual people needed within that call. Each laborer entry might include a Type (lead, rigger, loader, general labor, climber, machine operator) and a Quantity, letting a collaborator build out a complete labor call with as many sub-asset rows as they need.
Sub-assets support their own line item label configuration, so each entry renders clearly wherever it appears in tables and exports.
Asset Categories
Asset categories organize your asset type library. Like module categories, they are primarily an organizational aid and are not yet deeply surfaced as navigation or filtering in the UI.
Managing Asset Types
Asset types are managed in Event Settings alongside module templates. Click the event name in the top-left corner of the event, select Event Settings, then navigate to Asset Types in the settings sidebar.
Creating and managing asset types requires Event Admin rights. An asset type cannot be deleted if it is already referenced by a module template, an advance request, or a procurement record.
Open Event Settings
Click the event name in the top-left corner and select Event Settings.
Go to Asset Types
Select Asset Types from the settings sidebar.
Create a new asset type
Click Add Asset Type and give it a name, label, icon, and category.
Define properties
Add properties to capture the structured information each request for this asset should include.
Configure a sub-asset if needed
If the asset has nested, repeatable components, enable the sub-asset and define its label and properties.
How Asset Types Connect to the Rest of Advancing
Asset types exist at the configuration layer, but their value shows up throughout the advancing workflow. When a module template includes an asset request block, that block references one or more asset types. When collaborators fill out the advance, their requests carry the asset type's property structure. When those requests are reviewed, they can be approved, denied, or routed into procurement.