Skip to main content

Hide Client Prices from Team Members

  • January 19, 2026
  • 2 replies
  • 10 views

Marcia

I really need this to be addressed.

Currently, my team members are able to see the prices that clients paid for their services. This has consistently created issues, as contractors naturally compare those figures to their own compensation—without any visibility into overhead costs, operating expenses, taxes, or whether I am even able to pay myself in a given year.

This crosses significant professional boundaries for me.

It would be extremely beneficial—and frankly necessary—for team members to be able to see which services were selected and purchased, without seeing what the client paid for them. Knowing the scope of work is appropriate and operationally helpful; knowing revenue is not.

Pricing visibility is internal, sensitive business information. Sharing it with contractors who are not responsible for payroll, expenses, insurance, marketing, software, legal costs, or financial risk creates unnecessary tension and misunderstanding.

Please make this an option at the permission level so business owners can control what their team members are able to view. This would be a meaningful improvement for companies managing subcontractors and would help preserve healthy working relationships.

Thank you for taking this feedback seriously.

2 replies

Dannon Byrd
Forum|alt.badge.img+1
  • Newcomer
  • January 19, 2026

I couldn’t agree more with this needing to be an option. It’s like there needs to be a team member option somewhere less than an admin but more than moderator… Almost like a toggle option for on / off access to certain abilities each team member has. This is really big and needed. 


Alicia Bauer
Forum|alt.badge.img+4
  • Newcomer
  • January 20, 2026

@Marcia  - I completely understand why this is an important need, especially when you’re working with contractors and subcontractors. Having visibility into scope of work without exposing sensitive pricing and revenue details makes a lot of sense from both a professional and operational standpoint.

The best path forward right now would be to submit this as a Feature Request in the Ideas section of the community (or upvote this existing one that is similar). That allows the product and development teams to track how many users need this level of permission control and how critical it is for managing teams and maintaining healthy working relationships.

The more people who add their voice and upvote the request, the more visibility it gets—and the higher priority it tends to become for future updates.

This would be a really meaningful improvement for teams, and hopefully one HoneyBook will take seriously as more businesses scale. 💛