Your client opens the project tracker and the first thing they see is another vendor's logo. Not yours. The tool you pay for is doing the branding work you should be doing. For an agency, that's a small leak in every relationship.

Client portal project management fixes this by putting the work behind your own domain, your own logo, and access rules you control per person. This walkthrough is for agencies, consultancies, and freelancers who hand off project visibility to clients and want it to look like part of their own studio, not a third-party app.

Key takeaways

  • A client portal is a branded, role-scoped view of project work that lives on your domain, not your vendor's.
  • Zoobbe runs on a custom domain with automatic DNS and SSL setup, plus custom logo, colors, favicon, and footer.
  • You can hide Zoobbe branding entirely, so clients only see your studio.
  • Page sharing roles (viewer, commenter, editor, owner) and board visibility (private, workspace-only, public) decide exactly what each client sees.
  • White-label email runs through your own SMTP, so notifications come from your domain too.

What a client portal actually is

Strip away the marketing and a client portal is three things working together: a branded shell, scoped access, and a clear view of the work. Most agencies fake it with a shared Google Drive folder and a weekly status email. That works until the client asks where something stands at 9pm on a Thursday and nobody is awake to answer.

A real portal answers that question without you in the loop. The client logs in, sees the board, reads the latest comments, and knows what is in progress. You stop being the human refresh button.

Step one: claim your domain

The branding starts with the URL. Zoobbe supports a custom domain with automatic DNS and SSL setup, so your portal lives at something like projects.youragency.com instead of a generic app subdomain. The certificate provisioning happens for you; you point the domain and the SSL follows.

This matters more than it sounds. When a client bookmarks a link, that bookmark is your brand. When they forward it to their CEO, the CEO sees your studio's name in the address bar. The domain is the cheapest credibility you will ever buy.

Step two: make it yours

Custom branding in Zoobbe covers the parts a client notices: app name, logo, favicon, primary and secondary colors, custom CSS, and a custom footer. You can also hide Zoobbe branding entirely, so there is no "powered by" line undercutting the illusion that this is your own software.

For an agency, the color and logo work is usually a five-minute job once the domain resolves. Match your brand palette, drop in your logo, set the favicon, and the portal stops looking like a tool you rent and starts looking like a tool you built.

Step three: decide who sees what

This is where most DIY portals fall apart. You want the client to see their project and nothing else. Zoobbe gives you two levers.

Board visibility sets the wide boundary: private, workspace-only, or public. A client-facing board can be scoped so it is not visible to your whole workspace by default.

Page sharing roles set the fine-grained boundary. Share a page as viewer, commenter, editor, or owner. A client who should read updates and leave feedback gets commenter. A client who should only watch gets viewer. Permissions can inherit from the workspace or the parent page, so you set the rule once and the nested pages follow.

The result: one client never stumbles into another client's work, and nobody on the client side can edit something they shouldn't.

Step four: give them something worth looking at

A portal is only useful if the work inside it is legible. A few Zoobbe building blocks carry most of the weight here.

Boards and cards

Lists and cards with drag-and-drop, color-coded labels, priorities (Normal, High, Low, Urgent), due dates with reminders, and multiple assignees. A client glancing at the board can read status without a meeting.

Pages for the narrative

Cards show the moving parts; pages hold the story. Rich-text pages (built on Lexical) give you a place for the brief, the scope, the meeting notes, and the decisions. Nested page hierarchy keeps a multi-workstream engagement organized under one parent.

Comments and mentions

Threaded comments with @mentions keep the conversation attached to the work instead of scattered across email. The client comments on the card, not in a reply-all thread you have to forward to your team.

Real-time collaboration

Pages support real-time collaborative editing via Yjs CRDT, and you get live presence showing who is viewing or editing right now. When you update the brief during a call, the client sees it change without refreshing.

Step five: email that matches the brand

The portal isn't only what loads in the browser. Notifications count too. Zoobbe supports custom SMTP for white-label email, so digest and activity emails route through your own domain. The notification a client gets about a new comment comes from your studio, not from an address they don't recognize and might mark as spam.

You also get white-label OAuth (Google, GitHub) with your own client IDs, so the login screen carries your branding through the sign-in step instead of breaking the spell at the door.

Why this converts better than a status email

The honest pitch: a branded portal changes how clients perceive the work. The same project, shown behind your domain with your colors and a clean board, reads as more in-control than the same project described in a Friday email. Perception of control is a real part of what agencies sell.

It also cuts the support tax. Every "where are we on this?" message a client doesn't send is time your team gets back. The portal answers the routine questions so your people answer the strategic ones.

FAQ

Is a client portal a separate product I have to buy?

No. In Zoobbe it's assembled from existing features: a custom domain, custom branding, board visibility, and page sharing roles. You configure them into a client-facing setup rather than installing a standalone portal product.

Can clients see each other's projects?

Not unless you let them. Board visibility and page sharing roles scope access per board and per page. A client only sees what you share with them.

Can I remove all Zoobbe branding?

Yes. White-label lets you hide Zoobbe branding entirely and replace the app name, logo, favicon, colors, and footer with your own.

Will notification emails come from my domain?

Yes, if you configure custom SMTP. White-label email routes notifications through your own domain.

Do clients need to learn a complicated tool?

Clients usually interact with a board and a few shared pages. Viewers and commenters get a simple, read-and-respond surface, not the full admin view.

Build the portal your clients deserve

Your studio already does the hard part: the work. The portal just makes sure the client sees it the way you'd want them to. Spin up a branded board, scope the access, point your domain, and hand over a link that looks like it came from you. Start building your white-label client portal with Zoobbe.

Photo by Bench Accounting on Unsplash