Client Portal & Roles for Brand Guides
The client portal is where you manage your brand guides without touching the builder: see plan and usage, review design checks, set logo, imprint and visibility, invite people with the right role and reach support in one place.
What the client portal is
Brand guide software has two audiences. Designers and editors work in the builder. Everyone else needs answers: Which guides do we have? How much of the plan have we used? Who checked which layout last week? Where do I change the imprint? The Branddoq client portal answers those questions in one place, separate from the editing workspace.
Each customer sees only their own guides, their own plan and their own usage. The portal's interface is in German today; the guides you publish through it can be in any language.
What you see in the portal
Your guides
A list of every brand guide in your account with a direct way into the builder and to the published site under branddoq.io/{slug}.
Plan and usage
One overview of what your plan includes and what you have used: number of guides and pages, storage, design checks this month, AI credits from the plan and credits you have bought. No surprises at the end of the month.
Design-check history
Every AI design check you have run, with its verdict, findings and preview. Useful when a partner asks why their poster was flagged, or when you want to see whether a supplier is improving.
Guide settings
Per guide you set the logo, the imprint, the form of address used in the guide, office fonts for the typography chapter and whether search engines may index the guide. Guides are not indexed unless you say so.
Help centre and support
Guides, tips and FAQ in the portal, plus a support form. Support answers within one working day.
Roles: admin, editor, viewer
Branddoq has three roles. They decide who may build, who may only read, and who runs the account.
| Role | What it does |
|---|---|
| Admin | Full access, including account and user administration |
| Editor | Works in the builder: creates, edits and publishes guides |
| Viewer | Reads guides, does not edit |
Roles keep the guide safe from well-meant edits. A franchise partner gets viewer access and cannot move a module by accident.
Visibility per guide
Each guide is either public or protected. A public guide is reachable by anyone with the link. A protected guide asks for a password or a login before it shows anything. Downloads from the media pool follow the same setting. Search-engine indexing is a separate switch in the guide settings, off by default.
Plans
| Plan | Guides | Design checks | AI | Price |
|---|---|---|---|---|
| Trial | 1 (3 pages) | none | none | €0 |
| Standard | 1 | 5 per month | none | €69 per month |
| Premium | 3 | 100 per month | yes, 3,000 credits | €149 per month |
| Enterprise | unlimited | unlimited | yes, 10,000 credits | from €499 per month |
Prices include VAT. No minimum term, cancel monthly, payment via Stripe. Trial needs no credit card. Enterprise comes with an individual contract and a data processing agreement.
Hosting and privacy
Branddoq is hosted in Germany. Fonts are served from its own servers, not from a Google Fonts CDN. Only necessary cookies are set. A DPA (AVV) is available for every customer who needs one.
What the portal does not offer
- No single sign-on. Users log in with email and password.
- No API and no integrations with DAM, Figma or other tools.
- No custom domains yet. Guides live under branddoq.io/{slug}.
- No version history of guide content. Draft and published are the two states.
- The portal is in German today. An English interface is not available yet.
If these are hard requirements, Branddoq is not the right fit today. If you need a clear place for guides, usage, checks and settings with sensible roles, it is.
questions & answers.
A brand portal is the place where a company's brand guides and assets are published for employees and partners. In Branddoq the published guides under branddoq.io/{slug} are that portal. The client portal is the administrative layer behind it: plan, usage, checks, settings and users.
Three: admin with full access including user administration, editor for building and publishing guides, and viewer for reading only. There is no custom role builder.
Yes. Each guide is either public or protected by password or login. Protected guides also protect their downloads, and no guide is indexed by search engines unless you enable it in the settings.
No. There is no single sign-on today. Users log in with email and password, and roles control what they can do.
see it for yourself.