If you want a quick way to do this, create a related workspace.

Whenever you create a project, you automatically create a workspace for that project. Any participants that you add to the project will receive all emails or files sent through it.

If you need to send an email or file to just one person or a specific group of people related to the project, you can add related workspaces within your main project. These related workspaces allow separate communication lines that are only visible to the participants you add, while still keeping track of any activity, such as payments or signatures, under the main project. Here's how to create a related workspace.

Once you've added multiple workspaces within a project, you can switch between them by selecting the workspace at the bottom of the grey section labeled Only visible to you under Related Workspaces. Then, you can simply send a message or file from within that workspace.

If you connected your business email, any messages or files you send from a project will show as being from you and your actual email address.

If you haven't connected your business email, all emails and documents you send will still look like they come from you and your business name, but will actually be sent through a HoneyBook email proxy.

Pretty much any time! You're able to add attachments to emails you send through:

However, at the moment, you cannot add attachments to payment reminder emails.

At this time, photos cannot be embedded in emails/included in the body of messages. You can, however, add photos as email attachments.

HoneyBook looks at the sender, recipients, and threading of a message. If a message meets the criteria below, it will appear in the corresponding HoneyBook project’s activity feed, where you and the other project participants can reference the message along with other emails, important project details, files, and actions.

What messages will appear in a HoneyBook project:

What messages will not appear in a HoneyBook project:

If you or a client start a new thread from your email inbox, it will not appear in HoneyBook, even if you have email integration set up.

When there's new activity in a project that you own or are associated with—whether sent directly through the activity feed, or when files are sent and acted upon—here's when to expect an email notification regarding that activity.

The name used in your email signature is the same one you've listed in your personal account settings. To change what name is pulled into the email signature, change your name in your personal account settings.

The email that you use to log into HoneyBook is account-based, not company based. This means that you'll always use the same email as you toggle between your companies. The email listed in your account settings' account info is the email that you'll use across your companies.

Email integrations live under your Company Settings, which means you can integrate a different business email for each company. Here's how to connect a business email to HoneyBook.

This security protocol signs every email sent from your domain with a public key, so that the servers of those receiving your email can validate that the email was sent and authorized by you.

In other words, DKIM is like putting a unique stamp on all your letters. It helps prove that the email came from you and wasn’t changed along the way.

DKIM records are TXT records. A DKIM record includes both a TXT record name and TXT record value that contains the DKIM key. Both the record name and record value should be generated by your email provider and then added to the Domain Name System (DNS) settings of your domain provider.

Here is an example* of a DKIM record name and record value:

*Do not use the above DKIM record—this is just an example.

This security protocol defines a list of IP addresses that are permitted to send emails from your domain name.

In other words, think of SPF like a VIP list for your party (aka your email domain). It tells email servers which guests (mail servers) are allowed to send emails from your domain. When you send an email, the receiving server checks your domain’s SPF record to make sure the email is coming from a server on your VIP list. If it is, great! If not, it might mark the email as spam.

SPF records are TXT records that store information about your domain. SPF records will look different depending on how you configure them to behave.

Here is an example* of what an SPF record can look like:

*Do not use the above SPF record—this is just an example.

This security protocol builds upon SPF and DKIM by providing a way for email recipients to determine if an email message is legitimate, fraudulent, or suspicious.

In other words, you can think of DMARC as the boss that takes the rules from SPF and DKIM and decides what to do if the rules aren’t followed. It’s like setting house rules for what happens if someone crashes the party.

DMARC records are TXT records that incorporate both DKIM and SPF. Prior to setting up DMARC, you will need to make sure DKIM and SPF are set up for your domain.

Here is an example* of a DMARC policy record:

*Do not use the above DMARC record for your domain—this is just an example.

Effective February 2024, Google and Yahoo will be implementing stricter requirements for any businesses or entities that send commercial emails, in an effort to reduce email spam. Both platforms have already been blocking senders who have high spam complaints or missing domain records.

Start by verifying your email authentication through HoneyBook's DKIM and SPF domain tester. If the authentication fails, it’s crucial to follow the steps in the domain tester to update these records, as your emails are likely to go to spam otherwise. After verifying your DKIM and SPF, you can also check your DMARC settings to make sure it’s set properly as well.