We’re experiencing an issue with a custom object in HubSpot and wanted to see if anyone else has encountered something similar.
The issue
Some users receive the following error when trying to open a saved view:
“You need pipeline access to view this asset.”
Strange behavior
The bigger issue is that HubSpot is randomly switching the view back to Board View after some time. When that happens, the affected users are once again blocked by the pipeline access error.
We haven’t been able to determine what causes the view to switch back automatically.
Questions:
Has anyone experienced saved views automatically changing from List View to Board View?
Is this expected behavior for custom objects with pipelines?
Has anyone found a permanent fix, or is this something that requires HubSpot Support to resolve?
Any insights or similar experiences would be greatly appreciated.
Generally, when saving filtered views, HubSpot should stick to the view type that was saved. Create and manage saved views - if that’s not what you’re experiencing, I’d recommend flagging it with HubSpot support as a bug.
For some of the default views, since you can’t save over them, I’ve had unreliable behavior before, too.
Regarding the pipeline access, could you confirm if / why you’ve limited pipeline access for these users? (Settings > Objects > select Custom object > Pipelines > click on Pipeline > Actions > Manage access) - giving them access would at least, for the interim, allow these users to not lose access to their views.
In any case, support is the next best step here, yes.
Best regards
Moderator note: While this solution may not address the original poster’s specific situation, it could be helpful for other community members facing similar challenges.
We did confirm that the affected users have Core seats, so the pipeline access error itself is expected when the view switches to Board View.
The part we’re trying to understand is why the saved view is randomly changing from List View to Board View in the first place, as it was originally saved as a List View.
I’ve already raised this with HubSpot Support, and they’re currently investigating the behavior. I’ll update the thread once we have more information from them.
We did confirm that the affected users have Core seats, so the pipeline access error itself is expected when the view switches to Board View.
@Jaco15 I’m not following this conclusion - why would the pipeline access error be expected? I might have missed this in the past years as I typically hold higher roles in HubSpot portals but would not expect a Sales or Service seat to be a requirement for pipline access in general.
I’ve already raised this with HubSpot Support, and they’re currently investigating the behavior. I’ll update the thread once we have more information from them.
@karstenkoehler , that’s a fair point, and we’re currently working with HubSpot Support to determine whether the pipeline access error is related to licensing, pipeline permissions, or another underlying issue.
At this stage, we’re waiting for their findings, as the main issue we’re investigating is why the saved view is randomly switching from List View to Board View. Once we have a definitive answer from the Support team, I’ll be happy to update this thread.
We are dealing with a version of this now. My views did not change from table to board, but all of my team’s views switched to Board view overnight about a week ago. When they try to change them back, it will work for a minute, then revert back to Board. We started with a standard set of views (we use a prescribed order of views in Contacts, Tasks, etc.). But each advisor cloned the standard view, added a filter to just see their records, then saved them as a cloned view. These are the ones that suddenly switched to board view. Mine did not because mine are the original set. The helpdesk articles say to go into the settings in Index Customization and drag the “standard view” to the left and save it. But since everyone is using cloned views, this doesn’t work. The fix we have had to use is for everyone to switch to Table view, save it (which doesn’t save), then clone it again as a new view with a “-1” after the title. This seems to stay in Table view. They drag it over where it needs to be and delete the old one.
The issue is that we are very busy and don’t have time to re-create all of our views. There should be a universal default that a SuperAdmin can use to set all views (original and cloned) to a certain view type. Or just remove whatever is causing the views to revert and not be saved in a different view type.
