Custom asset fields allow you to capture organizational context that is shared across all submissions targeting the same asset. They are designed to store static, asset-level information such as asset ownership, responsible development team, business unit, environment, or region.
By defining this context once at the asset level, you avoid repetitive mapping on individual submissions and ensure data remains consistent across reports. This makes custom asset fields especially useful for maintaining accurate ownership, routing, and reporting as your asset landscape grows.
🔓 Subscriptions: Core, Premium, Enterprise
Configure custom asset fields
⚙️Roles: Company Admin
Custom asset fields are configured at company level and apply to all assets across your organization.
Go to Admin > Assets.
Click Manage custom fields.
Click Add custom field
Click Create a custom field.
Enter a name for the field and define options.
Save your input.
Once saved, the field becomes available on all assets and can be managed from the Custom fields overview. Existing fields can be edited to update the field name or adjust dropdown options. If a field is no longer needed, it can be archived so it no longer appears on assets or in exports.
Complete custom asset fields
Custom asset fields are completed when managing assets.
Go to Admin and open Assets.
Open the dropdown of the custom field you like to update.
Select an option.
💡Note: Custom asset fields can be updated in bulk. To do this, select one or more assets in the assets table, then click Edit assets in the action bar to update the custom field values for all selected assets at once.
The information entered is stored with the asset and is available wherever the asset is referenced in the platform.
Best practices
Use custom asset fields for stable information that applies to the asset itself, such as ownership, environment, or internal identifiers.
Avoid duplicating submission-level information in asset fields, as this can lead to outdated or conflicting data.
Review asset fields periodically and archive fields that are no longer relevant to keep asset data clean and usable.