Insights

A brand portal and a visual library are not the same system

A brand portal publishes assets that are already approved, so people can take the right logo or image without asking. Photography spends most of its life before that point, while frames are selected, reviewed and cleared. The decisions made then are what a portal cannot hold, because it begins where approval ends.

Mist drifts across a limestone ridge, pines rooted along the rock and the far side of the slope fading into white.

Photo: Martin Bissig

Photo: Martin Bissig

A brand portal is where a company publishes assets it has already approved, so that anyone inside it, or at a partner, can take the right logo, template or image without asking. A visual library is where images are kept while they are still being selected, reviewed and cleared, together with the decisions made about them.

A portal is built for assets that are stable and few

A portal serves logos, typefaces, templates and guidelines: few, stable and finished. A logo arrives finished and stays finished. Its job is to get the right version to a regional team without a request through headquarters, so assets are curated and access is broad by design. Those are the right choices for that job, and the reason it fits photography badly.

Photography's decisions are made before the portal begins

Photography's work happens before anything is finished. Two thousand frames become forty that matter and six that run, through selection, crop mark-ups, a rights check and a sign-off. None of it belongs in a portal, because a portal begins where approval ends. So the work happens in a shared drive, a review tool or an email chain, and only the six survivors reach the portal.

What falls between the two systems is the record. When someone later asks what an image was cleared for, the portal can say it is approved. It cannot say approved for what, by whom, or until when, because it was never in the room. A library built for the earlier half keeps the decision attached to the asset as it is made. A team may well need both, and the mistake is assuming the second is a feature of the first.

The moodcase review view of a photographer's Montenegro project. The misty limestone ridge from the top of this article fills the stage, selected in the strip beside the next frames from the same trip, each still without a status.

What moodcase does with this

moodcase Visual Asset Management sits in the earlier half. Selection, review and approval happen on the asset, and the state is recorded rather than inferred. Workflow Statuses carry an image's state through a team, and Activity & Audit Logs record who changed it. Nothing here replaces a brand portal. The two answer different questions about the same image.

Where this fits

If your portal can tell you an image is approved but not what it was approved for, the decision was made in a system that did not keep it. In moodcase the approval is recorded on the image as it happens, so the answer is still beside the image months later.

Visual assets need more than a folder. See how moodcase handles the full workflow.

Try all features for 7 days. No credit card required.

Delivery

Approval

Marketing Teams

Brands