Hi @JBradley2,
You are right to notice the change. What you used before did exist, but the behavior has changed with the new Sales Workspace.
In the previous version, if you were a Super Admin with a Sales seat, you could switch views and see the workspace as another user directly from the dropdown. That made troubleshooting and training much easier.
With the new Sales Workspace experience, HubSpot has tightened things up. For newer accounts or accounts that have switched to the updated workspace, the “view as user” feature is no longer available in the same way. HubSpot now clearly directs users to “log in as another user” if they want to see that exact experience.
The catch, though, is that the login-as-user feature usually requires enterprise-level permissions. This is why you’re told it’s your only option.
So yes, what you’re hearing is mostly correct. It’s not that you’re missing a setting; it’s that the feature has been limited based on:
- Workspace version (old vs new)
- Account setup date
- Subscription tier (especially Enterprise for user impersonation)
That said, there are a few practical ways to navigate through this:
First, check if you can temporarily switch back to the old sales workspace if your account still allows it. Some portals still have this toggle in settings, and it restores the dropdown-based “view as user” behavior.
Second, focus on permissions and filtered views instead of full impersonation. While it’s not a perfect replacement, creating saved views based on owner, team, or pipeline can often get you 70 to 80 percent of the way there when addressing issues.
Third, and most commonly practiced, is what you mentioned (logging in as the user), but doing it selectively instead of all the time. Many teams combine this with screen recordings or quick screen shares from reps to limit constant switching.
The overall change reflects many of HubSpot’s newer updates: features that were once more adaptable are now more closely linked to seats and tiers. The new workspace aims to boost individual productivity, not admin visibility, which is why this feels like a step back from an operations viewpoint.
So you’re not missing anything. This is one of those situations where the product has changed, and the workflow hasn’t quite adjusted yet.
Hope this helps!