Open any asset from the Assets panel and the canvas beside it is where the asset’s own record lives: what it is called, how it is described, which labels it carries, whether someone has approved it for marketing use, and — the part people come back for — every page, form, email template and profile that references it. This page covers the fields and buttons that are the same for all four asset types. The type-specific parts, the player and the preview, are on uploading images and video, audio and document assets.
Labels, marketing approval and usage tracking are ungated — they work the same on every plan, including Free.
Edits save themselves
Not everything waits. Ticking a label or a player setting saves immediately, with no delay at all, because there is no half-finished state a checkbox could be in. The Marketing approved checkbox is the exception: it goes through the same three-quarter-second delay as the text fields, so a very fast tick-then-navigate can outrun it.
The fields, by asset type
Not every field exists for every type, and the differences are not arbitrary — an SVG has no alt text worth generating, a PDF has no dimensions, an image has no playback options.
| Field | Image | Video | Audio | Document | What it does | Where it surfaces publicly |
|---|---|---|---|---|---|---|
| Name | ● | ● | ● | ● | how the asset appears in the library, in search and in every picker | it is the link text in the document snippet; otherwise internal |
| Alt Text | ● | — | — | — | the description a screen reader announces; written for you on upload and editable after | the alt attribute of every placement |
| Description | — | ● | ● | ● | internal notes so you recognize the asset later | nowhere — it is metadata, not published copy |
| Filename | — | — | ● | ● | the original file’s name, shown read-only under File Details | the name a visitor’s browser gives the download |
| Labels | ● | ● | ● | ● | groups the asset with the pages and content of the same campaign or topic | nowhere directly; it drives the picker’s label filter |
| Marketing approved | ● | ● | ● | ● | records that someone has cleared this asset for use | nowhere — it is a signal to your team |
| Player settings | — | ● | ● | — | controls, autoplay, muted, loop | written into the embed the snippet produces |
| File Details | ● | ● | ● | ● | created date, and dimensions or filename and type depending on the asset | nowhere |
| Used in | ● | ● | ● | ● | every place Leed knows this asset is referenced | nowhere |
Video, audio and document assets also carry a Transcript or Extracted Content section holding the text Leed derived from the file. Reading it needs Starter; capturing it does not. Transcription and text extraction covers both halves.
Labels
The labels here are the same labels you use on pages and page types — one vocabulary across the workspace, so a campaign’s images sit with its pages rather than in a parallel system of their own. Pick them from the Labels section; the heading carries a count once anything is selected.
Two labels are deliberately missing from the picker, because Leed manages them itself: the marketing-approved label, which the checkbox below the fields owns, and the profile-image label, which is applied automatically to a picture uploaded as somebody’s profile photo. Leaving them out of the list is what stops a hand-applied tick from disagreeing with the checkbox.
Labels are worth applying even if you never filter by them here, because the asset picker in the editor does filter by label — see labels and series for how the same labels behave across the rest of the workspace.
Marketing approved
Marketing approved is a checkbox, not a workflow. Ticking it applies a reserved label to the asset; unticking it removes that label. That is the whole mechanism.
Copy HTML Snippet
One button at the bottom of the asset, four different outputs depending on the type. It copies a ready-to-paste block of HTML for the asset as it stands, including its current player settings.
- Image
- Video
- Audio
- Document
A lazy-loading <img> at the original variant, carrying the real pixel dimensions so the browser reserves the right space before the picture arrives, plus the asset id and the alt text you set.
<img loading="lazy" src="/cdn-cgi/imagedelivery/CkSmQAGqpZ-mcWDDI6mu0w/8f2c.../original" width="1600" height="1067"
data-assetid="a1b2c3d4" alt="Sunrise over a ridge of low hills" />An SVG picks up one extra attribute, data-responsiver="false", which tells the responsive-image pass to leave it alone — a vector has no widths to generate.
The Stream player, wrapped in a div whose top padding reproduces the video’s aspect ratio so the page does not jump as the player loads.
<div style="display:flex; position: relative; padding-top: 56.25%">
<iframe data-assetid="a1b2c3d4" src="https://customer-56fx8oxwdrk14ngj.cloudflarestream.com/9e77.../iframe?autoplay=true&muted=true"
style="border: none; position: absolute; top: 0; height: 100%; width: 100%"
allow="accelerometer; gyroscope; autoplay; encrypted-media; picture-in-picture;"
allowfullscreen="true"></iframe>
</div>Only player settings that differ from their defaults appear in that query string, so a video left on its defaults produces a bare /iframe URL with nothing after it.
A plain <audio> element pointing at the file’s /f/… URL, with whatever playback attributes the asset’s settings imply.
<audio data-assetid="a1b2c3d4" controls>
<source src="https://www.example.com/f/a1b2c3d4/quarterly-briefing.mp3" type="audio/mpeg">
Your browser does not support the audio element.
</audio>A download link. The download attribute is what names the file on the visitor’s disk, and the link text is the asset’s Name — so a document called “Q3 Whitepaper” produces a link that reads Q3 Whitepaper, not q3-whitepaper-final-v4.pdf.
<a href="https://www.example.com/f/a1b2c3d4/q3-whitepaper.pdf" download="q3-whitepaper.pdf" data-assetid="a1b2c3d4">
Q3 Whitepaper
</a>The /f/… URL in the audio and document snippets is your own site’s file route, not a third-party CDN address — asset delivery and protection explains what it does, and what it does not, protect.
Used in
Leed keeps a record of where each asset is referenced and shows it as up to four collapsible sections at the bottom of the asset, each headed with a count — Used in 3 Pages, Used in 1 Form — and each listing the referencing objects as links you can follow.
| Section | What creates the reference | Where each link goes | Blocks deletion |
|---|---|---|---|
| Used in … Pages | inserting the asset in a page body through the editor, or setting it as the page’s feature image or feature video | the page, open in the editor | yes |
| Used in … Forms | attaching the asset to a form | the form | yes |
| Used in … Email Templates | placing the asset in an email template | the email template | yes |
| Used in … Profiles | uploading the image as somebody’s profile picture | that person’s user record | yes |
A section you do not see is a section with nothing in it — an asset used only on pages shows one section, not four empty ones.
For pages, the reference is derived from the data-assetid attribute the editor writes when it inserts an asset, reconciled every time the page’s content is saved. That is the important detail behind the next section: a reference Leed cannot see is a reference that does not block anything. Paste a raw image URL into a page by hand, or hard-code one in a repository template, and no attribute is written, no tracking row is created, and the asset looks unused.
A profile picture is an asset like any other, which is why some images carry a Used in Profiles section — see your profile.
Why Delete is grayed out
The Delete button at the bottom of the asset is disabled whenever any of those four sections has an entry in it. One reference is enough; it does not matter which kind.
To delete an asset that is in use: open Used in, work through the list, remove the asset from each place named — take it out of the page, detach it from the form, swap it out of the email template — and the button becomes available. There is no override and no “delete anyway”.
Deleting also needs the privilege. asset:delete starts at the Content Publisher role, while asset:create and asset:update are held from Content Writer up. So a writer can upload assets and edit every field on this page but cannot delete one, which is usually what you want. Roles and permissions has the ladder and the privilege matrix the full grid.
I removed it from the page and Delete is still disabled
Three things to check, in order.
- Reload the asset. The button reflects the tracking record as it was when the asset loaded.
- Look past Pages. Forms, email templates and profiles each block deletion in exactly the same way, and it is easy to clear the pages and forget that the same image is somebody’s profile picture. Expand every section that is showing.
- Check the feature image. Setting an image as a page’s feature image creates a page reference just as inserting it in the body does. Removing it from the body does not clear that one.
What deleting actually does
Deleting is a soft delete, and three things happen at once.
The asset disappears from the library and from every picker immediately — the asset list filters out anything carrying a deletion date, so it is gone from the grid, gone from search, and gone from the editor’s Asset button.
Its duplicate-detection fingerprint is removed, so the same file can be uploaded again cleanly rather than being flagged as a duplicate of something you can no longer see.
The record is retained for 60 days, then a scheduled cleanup removes the underlying file for good. Until that cleanup runs, an existing /f/… link to a deleted document or audio file may still resolve; afterwards it redirects visitors to your site’s 404 page. So a delete is recoverable by support within that window, and permanent after it — but do not treat the window as a reason to publish a link and delete the file behind it.