Metadata schema
These fields are what every form, filter and search in this tenant is built from. The count beside each one is how many assets already carry a value for it.
No fields are defined yet.
Refine search
The filters the rail offers, in order. A field has to be facetable before it can appear here; switching one off leaves it searchable in the box and takes it off the panel.
Nothing is enabled, so the rail is empty. Switch something on below.
Asset types
A type decides which of the fields above an asset shows — so a video need not carry print-resolution fields, and an archive need not carry alt text. Uploads are sorted into a type by what kind of file they are.
No types yet — every asset shows every field. Adding one narrows the form for the kind of file it covers; anything not covered keeps showing everything.
Upload profiles
One per kind of intake — a photographer's drop, a partner's delivery. A profile says what is already true of everything arriving that way, which form those assets get, and whether they may be tagged automatically.
No profiles yet. Uploads arrive with no defaults, the form chosen by the file's type, and automatic tagging on.
Auto-import from the file
Cameras and editors write metadata inside the file — who took it, what it is of, what the exposure was. A mapping says which of your fields each of those fills, and it runs as the upload lands.
There is nothing to import into yet. Define a field above first — an import writes the tenant's own fields, and the read-only ones describe the file rather than what you know about it.
Nothing is imported yet. Uploads keep their embedded metadata in the file either way; a mapping is what brings it into a field you can search and edit.