The HoneyBook Client Portal is the client-facing version of a HoneyBook project. It gives the client a centralized place to view selected files, messages, invoice/payment information and project details without exposing the business owner’s full HoneyBook workspace.
That distinction is important.
A client using HoneyBook does not automatically become a HoneyBook member with access to the business’s CRM.
They are interacting with their own project relationship.
What Clients Can See
HoneyBook’s current February 2026 documentation says portal users can access several areas.
The Activity area can show files sent and communication activity.
The Files area contains shared documents, attachments and bookmarks.
The Payments area provides access to invoice files.
Shared notes and project details can also appear when the business has chosen to make them visible.
This gives the client one consistent location for project information.
What Clients Cannot See
HoneyBook specifically provides an internal section marked Not visible to clients.
Information stored there is available to the business and authorized internal team members but not the client.
That can be used for private administrative context that should never appear in the external experience.
This separation is fundamental to using the portal correctly.
Clients Can Upload Files
Current portal functionality also allows clients to attach their own images or files.
For many service businesses, that removes another email-based workflow.
A designer might receive brand assets.
A photographer might receive a planning document.
A consultant might receive requested supporting files.
The material remains connected with the project rather than living in a detached email chain.
Portal Messages
Clients can participate in HoneyBook project communication through the portal.
Messages associated with the project remain visible alongside other project activity.
This helps keep the relationship organized, especially for projects spanning several months.
Invoices and Payments
The portal is also part of HoneyBook’s payment experience.
Clients can open invoice files and access payment-related information associated with the project.
If a saved payment method needs to be changed, HoneyBook currently directs clients through the relevant invoice/payment file in the Client Portal.
That means the portal is more than a project-information page.
It can participate directly in active financial administration for the client.
Contracts and Other Shared Files
Contracts, questionnaires, proposals and other HoneyBook Smart Files shared with the client can remain part of the project experience.
The portal therefore becomes useful after the initial email containing a file has disappeared deep inside the client’s inbox.
Rather than searching for “that contract from three months ago,” the client can return to the project environment.
The Portal Can Be Branded
HoneyBook allows account owners and super admins to customize the Client Portal login screen.
Current options include branding elements such as background color, logo visibility, company name and custom text.
That means the client experience can look more like the service provider’s own business rather than a completely generic software page.
Branded Does Not Mean the Business Built the Technology
A customized portal can display the service provider’s branding while still being powered by HoneyBook.
That distinction matters to clients encountering a payment or contract page.
The professional providing the service controls the client relationship and project.
HoneyBook supplies the software infrastructure.
How Clients Reach the Portal
HoneyBook allows businesses to include a portal link in emails and files, and authorized users can also share their portal according to account settings.
Clients should use the invitation or project link provided by the business they hired.
An independent HoneyBook information site should never ask a customer to enter payment details into an imitation portal.
The Portal Is Project-Centric
This is worth emphasizing.
The Client Portal is not primarily a public HoneyBook directory.
It exists around the client’s relationship with a particular HoneyBook business and project.
That is why its contents vary dramatically.
One client may see a photography contract, payment schedule and questionnaire.
Another may see consulting documents and recurring invoices.
HoneyBook provides the infrastructure, while the business decides which client-facing material exists.
Client Portal vs. Smart File
These concepts overlap but are not identical.
A Smart File is a specific interactive document or workflow.
The Client Portal is the broader project-facing area where shared files and other information can be found.
A single portal may therefore contain multiple Smart Files across the project lifecycle.
Client Portal vs. Business Dashboard
The business dashboard contains internal CRM and project-management information.
The client should not see:
- unrelated clients;
- the business’s full pipeline;
- private team notes;
- internal project information;
- account-level financial settings.
The portal exists to provide a controlled boundary between internal operations and client collaboration.
Payment Security
If a client receives a HoneyBook invoice or payment request, payment should be completed through the authorized project experience provided by the actual service business.
[PUBLICATION NAME] cannot verify a particular contract or transaction and will never ask a client for:
- card number;
- bank credentials;
- HoneyBook password;
- authentication information.
Contact the business named in the actual project if there is uncertainty about a charge or invoice.
One Project, Two Views
The HoneyBook architecture can be summarized simply:
Business View
CRM, pipeline, internal project details, private notes, financial administration.
Client View
Shared files, relevant messages, invoices/payments, visible project details and authorized uploads.
Both views refer to the same client relationship.
They simply expose different information to different audiences.