Custom fields let you add structured metadata to your Assets beyond basic tags and names. They're perfect for tracking information that's specific to your organization—like approval status, campaign names, expiration dates, or product SKUs.
Admins can create and manage custom fields. All users with Library access can view and edit field values on Assets.
How custom fields differ from tags
Tags are flexible, freeform labels—great for general categorization but without structure or validation.
Custom fields are structured data with defined types:
A "Status" field might only allow values like "Draft," "Approved," or "Archived"
An "Expiration Date" field ensures dates are entered correctly
A "Campaign" field can enforce consistency across your team
When to use custom fields
Custom fields work well for:
Workflow tracking: Mark Assets as draft, in review, approved, or archived
Categorization: Assign Assets to specific products, regions, or departments
Compliance: Track license types, usage rights, or expiration dates
Organization: Add project codes, campaign names, or version numbers
Filtering: Create precise filters to find Assets matching specific criteria
Custom fields and search
Custom field values are indexed and searchable. When you search in the Library, Lingo includes custom field content in the results. You can also filter specifically by custom field values.
Custom fields in Kits
Custom field values set in the Library carry over when Assets appear in Kits. However, you can only edit custom field values from the Library—not directly within a Kit.