Public search portal: when it is truly needed

When you ask "do we need a public lookup portal?", the underlying question is: is the number of external people needing access to the brand assets large enough that self-service is more cost-effective than manual management? If it is large enough, then yes. If not, then don't open it, as a public portal comes with maintenance costs and version control responsibilities that many brands underestimate.

What is a public portal and used for what?

The public search portal (brand portal or developer portal) is where partners and third-party developers can access official assets, usage laws, and integration guidelines without needing to ask the in-house team. No account is required, and no permissions need to be requested each time.

The practical purpose: to ensure that all parties are using the latest version. When brand guidelines are in a PDF file sent once via email, that version will become outdated in a few months, but partners will continue to use it because they are unaware of a new version. The public portal addresses this issue by turning documents from a "downloadable file" into a "living source" that is always updated.

Factors that determine whether to open or not

• Number of external partners and developers: This is the most important factor. If the number of external people needing access to assets is large enough that granting permissions to each becomes a burden, a public portal makes sense. If there are only a few partners, manual management is easier and more controllable.
• Frequency of needing new assets: If the brand frequently updates colors, identity systems, and usage guidelines, there is a high risk of partners using outdated versions. A public portal reduces this risk.
• Is there a digital product open for third-party integration? If you have a public API (open application programming interface), external developers need technical documentation and accompanying assets to build according to brand standards. This is a case where a public gateway is almost mandatory.
• Need to separate access rights: Not all assets should be public. Some are for internal use only, some are open to partners, and some are fully public. If access rights are complex, a layered access portal is more suitable than a simple public portal.
• Who will maintain the portal: The public portal needs regular updates. If there is no staff assigned to this task, the portal will become outdated and counterproductive.

When to choose which direction

Brand rules should not be dead in a downloaded file. Anyone who needs them must find the latest version, not an outdated one from two years ago.

Sinh Vũ, A2 cascade

Common errors when deciding to open a portal

• Open for show, not real need: Seeing large brands with public portals and following suit without having enough external partners. The result is a page with few visitors but requiring many resources to maintain.
• No separation of rights before opening: Exposing sensitive assets because it is unclear what is public and what is not.
• Building and then neglecting: A well-built portal without an update process. After six months, partners find outdated information and lose trust in both the portal and the brand.
• Lack of accompanying usage guidelines: Assets are uploaded but without contextual guidance, partners still do not know how to use them correctly and have to ask.

Sinh Vũ's viewpoint

Sinh Vũ builds a higher-level search portal, specifically an interactive portal or digital asset management system, precisely when clients with a large partner network need a single common source. Salesforce is a prime example with the Lightning Design System, a completely open design system for third-party developers to build to standard without needing to ask directly.

However, if the client team is small and has few external partners, Sinh Vũ will be straightforward: there is no need to open a public portal. A clearly versioned PDF sent through a controlled channel is sufficient and much easier to maintain. The question is always: the cost of maintaining the portal versus the self-service value it creates. When those two are not balanced, do not open.

Sinh Vũ does not accept the creation of complex digital asset management systems outside of high-level consulting. However, Sinh Vũ will help you clearly identify which thresholds are worth investing in and what needs to be prepared before launching.