When an Asset can appear in multiple Kits, it's helpful to know where each Asset is exists so you can keep things organized. You can also see where assets are being used from and by who. So if your logo exists in multiple kits, you can optimize you setup by analyzing where people are actually using it from.
Checking where an asset exists
To see where an Asset is used:
Select the Asset (either in the Library or within a Kit)
In the inspector panel, find the Kits section
You'll see a list of all Kits containing this Asset
See where an asset is being used from
Beyond just seeing which Kits contain an Asset, Asset insights show you:
How often the Asset is viewed
How often it's downloaded
Trends over time
This helps you understand not just where an Asset appears, but how actively it's being used.
To see usage details for an Asset:
Select the Asset (either in the Library or within a Kit)
In the inspector panel, select View insights
In the asset insights modal, open the Kits tab
You'll see a list of Kits from which this asset has been used from in the selected time period
Note that only Admins and Content Managers can access insights.
Why usage tracking matters
Understanding usage helps you:
Avoid breaking changes: See what Kits will be affected before editing or deleting
Maintain consistency: Know where an Asset appears so updates reach everywhere
Clean up unused Assets: Identify Assets not in any Kits
Understand reach: See how widely an Asset is distributed
Finding unused Assets
To find Assets that aren't in any Kits:
Open the Library
Select the "Unsued assets" view
Note that only Admins and Content Managers can access the Library.
The single-source model
Remember that Lingo uses a single-source model:
One Asset, many references: The same Asset can appear in unlimited Kits
Changes apply everywhere: Update the Asset once, and it updates in all Kits
Metadata is shared: Tags, custom fields, and notes are the same across all Kit appearances
This means an Asset with high usage is especially important to maintain carefully—changes affect more places. If you need to, you can also create a duplicate to have a separate version for different contexts.