HoneyBook can expand from a solo business account into a team environment with differentiated roles and permissions. Current HoneyBook documentation defines several access levels, including Basic, Moderator, Admin, Super Admin and Owner, while bookkeepers receive a specialized financial-access model.
The number of additional team members also depends on the membership plan.
Starter currently supports no additional team members, Essentials supports up to two, and Premium supports unlimited team members.
That makes team structure a genuine product decision rather than simply a matter of sharing one HoneyBook password.
Never Solve Team Access by Sharing Credentials
Each team member should use an appropriate authorized user rather than signing into the owner’s account.
HoneyBook’s security guidance says individual users should maintain unique security phone numbers for verification to avoid authentication conflicts between users.
Separate accounts also allow HoneyBook to enforce permission boundaries.
If everyone uses the owner credential, the company loses those controls.
Basic Team Members
Basic is the most restricted ordinary team role.
Current HoneyBook documentation says Basic users can work with projects they create or are added to, but they cannot freely see every other teammate’s pipeline, contacts or projects. They also cannot administer areas such as team roles, bank information or broader pipeline configuration.
That can make sense for someone who needs to handle assigned client work without receiving access to the entire company.
Moderators
Moderators expand visibility.
HoneyBook currently says Moderators can see other team members’ workspaces and pipelines, view contacts created by other users and view broader project information.
Their administrative authority is still limited compared with the higher-level roles.
For example, Moderators do not receive the same authority over the client portal, pipeline customization or team-role management.
This makes the role useful when someone needs oversight without full company administration.
Admins
Admins receive broader operational control.
HoneyBook’s current file documentation says Owners, Super Admins and Admins can edit team members’ Smart Files, while Basic and Moderator users cannot do so without a permission change.
That distinction is useful for managers who need to intervene in client work created by another team member.
An assistant responsible only for their own projects does not necessarily need that access.
Super Admins
Super Admin is a high-access role.
Current HoneyBook documentation says Super Admins can perform company-wide actions such as customizing pipeline stages and the Client Portal, accessing reports and bookkeeping, creating or sending files from projects they are not already participating in, and managing project notes more broadly.
The role should therefore be reserved for people who actually need broad company visibility.
It is not merely a title of seniority.
It changes what sensitive information and administrative tools the user can access.
Owner
The Owner sits at the highest account level.
Some HoneyBook controls are specifically reserved for Owners or shared only with Super Admins.
For example, current pipeline documentation says only Owners and Super Admins can edit the company’s pipeline and create custom pipeline views.
Reports also have role-based visibility. Current July 2026 documentation says only the account owner has a complete view of the Reports page, while team-member reporting can be limited to the projects they created.
Contact Visibility Also Depends on Role
HoneyBook’s July 2026 contact documentation gives a useful example of the permission model.
Moderators, Admins, Super Admins and Owners can see all team contacts, while Basic users can see contacts they created or contacts connected to projects they share. Private notes remain visible only to the person who created them.
This prevents a Basic user from automatically receiving the organization’s entire contact database.
Project Notes Have Their Own Permission Logic
Notes demonstrate that permissions are not simply all-or-nothing.
HoneyBook’s current documentation says any teammate participating in a project can work with notes inside that project, while access to notes in projects they have not joined varies by role.
A Basic user generally cannot access those unrelated notes.
A Moderator may view more.
An Admin can have additional editing capability.
A Super Admin receives still broader access.
This is useful for teams where internal project history can contain sensitive client context.
Bookkeeper Access Is Different From Employee Access
HoneyBook has a specific bookkeeper access option.
Its current documentation says bookkeepers can receive the financial information needed for their job without gaining unnecessary access to the owner’s broader project environment.
HoneyBook also says the normal plan limit on team members does not apply to bookkeepers in the same way.
That means a solo HoneyBook owner does not necessarily need to make an accountant a normal project collaborator just to share financial reports.
Expense Access Is Restricted
Financial permissions become especially important as HoneyBook Finance expands.
Current 2026 expense documentation says only Owners, Super Admins and Bookkeepers can create, edit or delete expenses and download expense CSV reports.
A salesperson therefore should not automatically have the same financial controls as the business owner merely because they use the same CRM.
Refund Permissions Also Vary
HoneyBook’s July 2026 refund guidance says only account Owners, file Owners, Admins and Super Admins can issue refunds.
This is exactly the kind of action that should be role-controlled.
Refund authority can directly move company money.
Multiple Companies Are Not the Same as Multiple Team Members
HoneyBook also supports a multiple company model for businesses operating several brands or entities on applicable plan configurations.
This is very different from simply adding coworkers.
HoneyBook says each company exists as its own entity with separate company settings, projects, bank accounts, integrations and other business data.
The companies can still exist under one broader HoneyBook account relationship.
What Is Shared Between Companies?
Some user-level elements remain shared.
Current HoneyBook documentation says personal account settings and login credentials can carry across companies the user is authorized to access. The subscription payment method is also managed through the main account structure.
This allows one owner to move between brands without maintaining entirely unrelated credentials.
What Remains Separate?
A great deal remains company-specific.
HoneyBook currently lists separate:
- company settings;
- reports;
- bank accounts;
- QuickBooks integration;
- projects;
- templates;
- contact forms;
- calendars;
- integrations.
This makes multiple companies substantially more useful for genuinely distinct brands.
A photography company and consulting company do not have to dump all clients and templates into the same operating environment.
Projects Cannot Simply Be Moved Between Companies
HoneyBook’s current documentation says projects cannot currently be transferred from one HoneyBook company to another.
That means the company structure should be designed carefully.
Creating projects under the wrong brand and assuming they can all be moved later can produce avoidable cleanup work.
Banking Is Configured Per Company
Each HoneyBook company also requires its payment-bank details to be configured individually.
HoneyBook says the same underlying bank information can potentially be entered for more than one company, but it must still be added within each company’s own settings.
That separation is important for businesses that actually keep different bank accounts by brand or legal entity.
QuickBooks Is Company-Specific Too
QuickBooks connectivity is similarly separate.
HoneyBook says multiple companies must be integrated individually rather than one connection automatically applying across every company profile.
That allows financial activity to remain aligned with the correct HoneyBook company.
Reports Do Not Automatically Aggregate All Companies
HoneyBook’s current reporting documentation says reports reflect the company profile currently being used rather than universally combining every company into one report.
An owner operating several brands should therefore understand that “HoneyBook report” may mean one company at a time.
This is operationally cleaner but changes how group-level analysis must be approached.
Premium Becomes More Logical as the Organization Grows
For a single-person business, advanced team controls may provide little immediate value.
As soon as the business adds:
a sales assistant,
project manager,
bookkeeper,
associate service provider,
or several brands,
the permission model becomes materially more important.
That is why Premium should be evaluated as an organizational tier rather than simply “Starter with more features.”
The Useful Team Model
HoneyBook team architecture is easiest to understand through least necessary access.
A team member should receive enough access to perform their job without automatically receiving the owner’s financial and administrative privileges.
Basic serves assigned work.
Moderators gain wider visibility.
Admins gain stronger operational control.
Super Admins can manage broad company functions.
Owners maintain the highest authority.
Bookkeepers receive specialized financial access.
Multiple companies separate different business brands rather than individual employees.
That structure is much safer than treating one HoneyBook account as a shared password for the whole company.