Brand portal and digital asset repository: a standard source

This question often arises when a business starts to have multiple teams, various communication channels, or is working with external agencies and printers for the first time. You send the logo and receive a poster with the wrong color logo. Upon inquiry, they took it from an old email. This is the clearest sign that the brand does not have a single source of truth for everyone to refer to.

Two tools, two roles

A digital asset library, or DAM (Digital Asset Management), is a system for storing all brand files: original logos, color sets, fonts, images, design templates, and guidelines. The difference from a regular shared drive is that DAM has three core features: role-based permissions (who can view, download, edit, and publish), version management (each update has a history, old versions are marked as outdated), and metadata search (information describing each file for quick retrieval without needing to remember the exact name).

The brand portal is the external presentation layer, often built on DAM or operating in parallel. Partners, printers, and media agencies accessing this portal only see the approved release files. They do not see drafts, outdated versions, and cannot edit the original files. The purpose of the portal is to reduce the burden on the internal team: instead of answering emails like "please send me the white background logo," you only need to send the portal link once.

When you need which one

Factors to set correctly

• Clear role-based permissions: Designers have the right to upload and edit. Marketers have the right to download and use. External partners can only view and download approved versions. Lack of clear permissions means the original may be altered without anyone noticing.
• Consistent naming and metadata rules: A large repository can be very useful, but it becomes useless if no one can find the needed files. A simple naming rule, applied consistently from the start, saves a lot of time later.
• The brand guardian responsible for updates: The tool does not operate by itself. A person is needed to clean up outdated versions, release new ones, and notify stakeholders.
• Release process, not just storage: When there is a new logo, the release process needs to be clear: who approves, who uploads to the repository, and how the old version is marked to prevent confusion.

Common errors

• Uploading all files to Google Drive or a shared drive without permissions or version control. Everyone can edit, even accidentally.
• Create a repository and then neglect it. After six months, the repository has two dozen versions of the logo and no one dares to confirm which one is the latest.
• Open editing rights too broadly out of fear of bothering users. As a result, the original document is altered without a traceable history.
• Do not name files according to a unified rule, as this leads to spending more time searching for files than it would take to recreate them from scratch.

Sinh Vũ's viewpoint

In the brand operations service, Sinh Vũ establishes a brand portal and digital asset repository right from the startup phase, before any content is released externally. The reason is not that this is a complex technical task, but because without a single source of truth, the gatekeeper has no ground to work from. You cannot identify discrepancies if you do not know where the correct version is.

A controlled brand is not about having a beautiful identity system, but about everyone in the organization knowing where to find the standard files and having no reason to save their own versions on their machines.

Sinh Vũ, service document O1

If you are at the initial stage, you don't need a complete DAM right away. A simple brand portal with clear permissions can solve most practical issues. More important than the tool is determining who is responsible for maintaining it.