Meta presets for customers and assets

Meta UI presets let you decide, up front, exactly what metadata your team should capture — typed fields (string, number, boolean, select, checkboxes) with required flags and min/max rules — and this release extends them from orders and subscription contracts to customers and assets. Customer presets can be scoped to individual and/or organization customers, and asset presets to images, videos or files, so an editor only ever sees the fields that actually apply to the record in front of them. On assets, the preset fields appear right in the image, video and file edit panels alongside the existing meta and reference sections; on customers, they replace the raw key/value input on the manage-customer form and render as a clean, aligned list in the customer information sidebar. Save is gated on preset validation, so required metadata can't quietly go missing — the CTA stays disabled until every required field is filled and re-enables the moment it is.

The practical payoff: metadata stops being tribal knowledge. Instead of hoping each person remembers to tag a product video with the right campaign key or spells a customer segment the same way twice, the shape is enforced at the point of entry — which means downstream filtering, search, integrations and reporting can rely on that data actually being there and actually being consistent.