A brand portal is one place where a company keeps its strategy, its guidelines, its logo files, and its approved components, all current. It replaces the brand book PDF, the shared drive of logo variants, and the person everyone messages to ask which file is right.
Most teams do not go looking for a brand portal until something ships wrong: last year's logo in a partner deck, or a freelancer working from a PDF that was superseded twice. The files were all there somewhere. Nobody could say which one was current.
This post covers what a brand portal holds, what belongs in each part, what to keep out, and who has to own it once it is live. The four parts below are the ones TrueKeep builds a portal around, and the setup guide walks through each.
Key Takeaways
- A brand portal holds four things: the strategy, the guide, the assets, and the approved components.
- The guide answers "is this on-brand?" without a conversation: hex values, logo clear space, type specs, and the words the brand avoids.
- Assets belong in the portal as the real thing, so colors render as swatches, logos at presentation quality, and typography in the actual typeface.
- A portal now has a second audience. Through an MCP connection, Claude, ChatGPT, and Cursor read the brand directly, so work comes out on-brand for people who never open the portal.
- A portal is only as current as the person who updates it, so name that person before launch.
What a brand portal is
A brand portal is a single online place that holds a brand's decisions and its files together, and keeps both current. A brand manager checks a claim against it. A designer downloads the approved logo from it. A new hire reads it in their first week instead of asking three people.
Public examples make the shape obvious. Mozilla's brand site puts the logo, the color values, and the voice guidance on one set of pages. The BBC's Global Experience Language does the same for a much larger organization, down to type scales and motion rules.
Two things a brand portal is not. It is not a brand book PDF, because a PDF is a snapshot that starts aging the day it is exported. It is not only a digital asset manager, because a DAM stores the files without carrying the reasoning that decides which file is right.
What belongs in a brand portal: strategy, guide, assets, and components
Four parts cover almost every question a team asks.
- Strategy. What the company is for, who it serves, how it positions itself, and what it will not do. This is the part people skip, and it is the part that settles arguments about tone.
- Guide. The rules: logo variants and clear space, color values, typography, imagery, and voice. Our brand guidelines template lists the sections in the order most teams need them.
- Assets. The approved files themselves, in the formats people actually place: SVG and PNG logos, the typeface files, photography, icons.
- Components. The pieces that get reused without redrawing them: a deck template, an email header, a button, a social frame.
A portal with all four parts answers both of the questions teams actually ask. The brand manager wants to know whether a piece of work is on-brand. The designer wants the file. Neither should have to ask a person.
Show the real thing, not a description of it
Portals get ignored when they describe the brand instead of presenting it. A color section that reads "Deep Slate, our primary neutral" makes a designer open a second tab to find the value. A color section that renders the swatch, states #2B3440, and offers the value for copy solves the problem where it appears.
The same rule holds across the portal. Logos appear at presentation quality, not as a thumbnail on a white card. Typography appears in the actual typeface, so a writer can see what the headline will look like before they commit to it. TrueKeep treats this as a design principle rather than a nicety.
The tradeoff is real work. Showing the real thing means someone has to upload the real thing, at the right size, with the right file behind it. A portal assembled from screenshots is faster to build and slower to use.
The part most portals leave out: the judgment
Every portal records what a brand looks like. Few record how it behaves. That is the gap that produces work that passes every rule and still feels wrong.
Judgment is specific and writable. It looks like this:
Words we avoid: disrupt, ninja, solutions.
Never put a product name in a headline.
Sentence case everywhere, including buttons.
We are direct with customers and formal with partners.
TrueKeep calls this the design brief: the decisions behind the brand, written down and kept current alongside the guide. Four lines of it settle more drafts than a page about consistency ever will.
A brand portal now has a second audience: AI tools
Most of the brand work in a company is now drafted in a chat window. The person writing a launch email in Claude or a campaign brief in ChatGPT is not going to stop, open the portal, read the voice section, and come back. So the brand has to reach them instead.
That is what an MCP connection does. The Model Context Protocol is an open standard for giving AI tools access to a source of information, and TrueKeep uses it to serve the brand. Connect Claude, ChatGPT, or Cursor once, following the AI connection guide, and the tool reads the strategy, the guide, and the design brief before it writes a word. TrueKeep also offers a downloadable brand kit skill that carries the brand into Claude, and a final pass that checks an output against the brand and fixes what is off before it ships.
This changes how you judge a brand portal. Logins used to be the measure of whether it was working, and now the people who never log in matter just as much. The guidelines come to the work.
What does not belong in a brand portal
A portal earns its place by answering questions fast, and everything you add slows that down. Keep these out:
- Campaign drafts, unapproved concepts, and "final v3" files. They belong where the work happens, not where the answers live.
- Retired logos and old color values. If you keep them for the record, keep them somewhere the record is the point, because anything in the portal will eventually get placed.
- One-off crops and exports. A file made for a single post is not a component.
- Contracts, invoices, and trademark paperwork. Those belong with your legal files.
The test for any item: would a person arriving with a question be glad to find it, or have to step past it?
Who keeps the brand portal current
A brand portal is only as current as the person who updates it. This is the failure mode behind every abandoned portal, and it is worth deciding before launch rather than after the first complaint.
Name one owner, then make updating cheap enough that the owner actually does it. If a color change needs a ticket and a developer, the portal will drift. TrueKeep handles this with edit mode, covered in the guide to making changes, so a curator changes a value in the portal itself.
Then put a review on the calendar. Once a quarter, walk the four parts and ask what is no longer true. It takes about an hour, and it is what keeps people from checking the portal and then checking with someone anyway.
FAQ
What is the difference between a brand portal and a DAM?
A DAM stores and organizes files; a brand portal holds the decisions as well as the files. A digital asset manager is built for search, permissions, and distribution at volume. A brand portal is built to answer "is this on-brand?" for a person who has 30 seconds. Some teams run both, with the portal as the front door.
What should a brand portal include?
Strategy, guide, assets, and components, plus the name of whoever keeps it current. The strategy explains the brand, the guide states the rules, the assets are the approved files, and the components are the reusable pieces. Anything past those four is optional.
Do we still need a PDF brand book?
Only for people who cannot access the portal, and then only as an export. A PDF goes stale the moment it leaves your hands, and you have no way to know who is still working from the old one. If a partner needs a document, send a link first.
How do I give Claude my brand guidelines?
Connect Claude to a source it can read, rather than pasting the guidelines into every prompt. With TrueKeep, that is an MCP connection: you connect once, and Claude reads the strategy, the guide, and the design brief before it drafts. Pasting works for one conversation and fails on the next one, because the next person pastes something different.
Who should have access to the brand portal?
Everyone who makes anything with the brand on it, which is more people than most teams assume. Sales builds decks, recruiters build job posts, support writes emails. TrueKeep covers everyone in the organization without counting seats, so you can include the people who need the brand only occasionally.
Where to start
A brand portal holds four things: the strategy, the guide, the assets, and the approved components. The guide answers "is this on-brand?" quickly enough that people ask it. The assets show the real thing rather than describing it. The design brief records the judgment behind the rules, which is the part a PDF never carries. And an MCP connection puts all of it inside the AI tools where most of the drafting now happens.
None of it survives without an owner. Name that person, give them a way to edit the portal directly, and review the four parts once a quarter.
If you are building one, start with the strategy and the guide, because they settle the questions that slow everyone else down. You can get started with TrueKeep and have the four parts in place before you load a single logo file.