Unfortunately, view-only seat users cannot use the BCC address to log emails, even though you as a core seat user can use it without personal email access.
The key restriction is that HubSpot requires “personal email access” for BCC functionality, and view-only seats don’t include this permission. So view-only users are blocked from this feature entirely, regardless of whether they’ve actually connected personal email or not.
@karstenkoehler hi - I have a question re this - in the above screen shot, one of the options is crm emails - if emails can’t be logged with a view-only seat, then what will they view when the option is toggled to ‘their crm emails’ - there will never be any right as they can’t log them? Or am I missing something there! Thanks
@M_Kelly a user might have had a core seat previously and logged emails – which would allow them to still view those emails with a view only seat Keep in mind that seat assignment can be temporary and potentially switched on a regular basis.
Thank you for posting your question @CMontgomery0 ,
The answer is Yes — view-only users can be assigned as contact or company owners. You can find more about Assigning ownership of records here: Assign ownership of records
So does this mean that the users we have who don’t actually need a Core seat cannot be downgraded to View-only, because they still need to be able to log emails and be assigned as Project Managers (one of our custom properties)?
They don’t really work in HubSpot at all, as they operate in Asana and Outlook and never need to access HubSpot themselves. However, others in our company need to be able to see their emails and assign projects to them.
@karstenkoehler, is correct. With a View-only seat, Users won’t be able to utilize the BCC address to log emails to the CRM. We can also see this noted in this Ideas post here https://community.hubspot.com/t5/HubSpot-Ideas/View-Only-Seat-Connect-email-with-HubSpot/idi-p/1065185
Regarding your custom ‘Owner’ property: you can still assign users to this field without issue. However, keep in mind that since this is a custom property rather than the default HubSpot Owner field, these users may face limitations when trying to take certain actions within the platform. If you’d like to dive deeper into your specific process, I may recommend starting a new Community post so we can help you streamline the process!