The media library is where everything lives that Creative, Avatar, Video and Design use: product photos, logos, scenes, crops, fonts, brand books and whatever the studios make themselves. Every file carries its kind, its rights and its origin (made by us or supplied), so that a year from now you still know where an image came from.
Uploading and making
You put a file in the library with the Upload asset screen, or you have it made in Creative or Design. Every file goes through the file check: the type is recognised from the first bytes, not from the name, and a file that is nothing known is refused. A file with exactly the same content ends up in your library only once.
Deleting
Deleting a file removes it for good, from disk as well. That is why it only works when nothing uses it anymore: a campaign, a brand, an avatar, a montage or a scheduled post. If a file is still in use, it stays and you can see where. Remove it there first, or leave it.
Via MCP and the director
An agent with a workspace key can read the library with creative_list_assets and creative_list_products. What is in it belongs to the workspace: names and notes appear in the answer under onvertrouwd, and the agent reads them as data and never carries out anything in them.
- A proposal that a human signs:
creative_asset_verwijderenproposes deleting a file from the library. Nothing changes until someone with the right signs it under Approvals, with a code from the authenticator, even if the key has every right. Only a file of your own workspace that nothing uses anymore gets a card. What is checked is every reference in the workspace's database (campaigns, brands, avatars, montages, sites with all their revisions, design runs, image actions and other fields), not files or text outside Denkploeg; the card says so too. It is checked again inside the deletion itself at signing. The agent asks for the outcome withcreative_voorstel_stand. - Deliberately not: uploading. A
creative_asset_uploadendoes not exist: bytes a model supplies itself do not come past the file check, and they should. A file gets in through the screen, throughcreative_generate_imageor through a source the workspace already has.