Most software gets designed for the person who set it up, not the person who lives in it all day. The admin who built the portal knows where everything is, so the clutter never bothers them. The coordinator who opens it for the fortieth time this morning has to look past six things they'll never touch to find the two they need. That gap is where adoption quietly dies.
If you run HubSpot for a student accommodation or BTR operation, this is a problem you can now fix in settings rather than working around. HubSpot released personalised navigation in beta in June 2026, and for property teams it's more useful than the announcement made it sound.
Open a typical operator's CRM as a leasing coordinator and here's what you see: Marketing Hub, Content Hub, Operations Hub, a full reporting suite, workflow tooling, integration settings. None of it is their job. Their job is the enquiry that came in ten minutes ago and the viewing they're trying to book off the back of it.
Every menu item that isn't part of that job is a small tax. It's a moment of hesitation, a wrong click, a "where do I find the deals again?" message to whoever set the system up. Individually these are tiny. Across a leasing team during a peak booking cycle, they add up to a system people tolerate rather than one they actually use — and a CRM your team works around is a CRM that stops telling you the truth about your pipeline.
The instinct is to blame training. Usually it's not a training problem. It's a design problem. You're asking front-line staff to carry the full complexity of a platform built for six departments when they only work in one.
Personalised navigation lets an admin configure navigation templates by role and apply them to a team. Instead of everyone inheriting the same sprawling menu, each user sees a nav built for what they actually do.
Before this, getting anywhere near role-specific views meant permission-set gymnastics or simply living with the clutter. Now it's native. No development, no third-party workaround, no custom build — you define the template, assign it to the team, and that team's navigation shrinks to what matters.
It's currently in beta, which matters for how you roll it out (more on that below), but the core capability is exactly what a multi-team property operator has needed for years: the ability to make one platform feel like the right tool to every person using it.
The point isn't to hide things for the sake of it. It's to match each role's navigation to the journey that role actually runs. Here's how I'd set it up for a property operator.
Leasing: Contacts → Conversations → Deals. Nothing else in the way. This is the enquiry-to-booking path and it's the only journey a leasing coordinator runs all day. A prospect enquires, the conversation happens, the deal moves toward a signed tenancy. Strip the nav to those three and the tool finally matches the task.
Marketing: Campaigns → Forms → Reporting. The people running your enquiry generation don't need the deal pipeline front and centre, and they definitely don't need workflow internals. They need to launch, capture, and measure.
Operations: Workflows → Properties → Integrations. This is where the machinery lives — the automations, the custom objects, the connection to your PMS. Keep it available to the people who maintain it and out of everyone else's line of sight.
The leasing view is the one worth getting right first, because it's the highest-volume, highest-turnover role in most PBSA operations. Every extra item you remove from that nav is friction you've taken out of the job your occupancy depends on.
Adoption is the number one failure mode of CRM rollouts. Not the migration, not the integration — whether people actually use the thing once it's live. A clean, role-scoped navigation is one of the cheapest ways to move that number.
The first win is at go-live itself. That's the highest-pressure week of any implementation: bookings still coming in, staff learning a new system, no patience for friction. If a leasing coordinator opens HubSpot on day one and sees exactly the three areas they need, the "where do I find X?" questions largely disappear. The system feels like it was built for them, because it was.
The second win keeps paying out. PBSA leasing teams turn over seasonally — you onboard new starters ahead of every booking cycle, sometimes several at once. A role-scoped nav makes each of those onboardings faster and closer to self-serve. A new coordinator doesn't need a guided tour of every screen in the platform. They need to understand three areas, and three areas is what they see. That's the difference between someone being useful on day one and useful in week three.
Because it's still in beta, treat it the way you'd treat any change to a live system that your team depends on. Start narrow.
Configure the leasing template first, apply it to one team, and leave your admins on the full navigation so nothing they rely on disappears. Let it run through a booking cycle. Ask the leasing team whether anything they genuinely need went missing — it rarely does, but the point is to find out on one team rather than across the whole portal. Once it's proven, extend the pattern to marketing and operations.
This is the same discipline that works for any HubSpot change: make the smallest useful change, watch it in the real world, then expand. Navigation is low-risk as changes go — you're hiding menu items, not deleting data — but a staged rollout still beats flipping it on portal-wide and fielding surprises during your busiest week.
Personalised navigation won't transform your business on its own. What it does is remove a layer of daily friction that's been quietly costing you adoption, and it does it in an afternoon. For a platform your leasing team is supposed to live in, that's a good trade.
If you're rolling out HubSpot for a leasing team, or your portal has grown cluttered and adoption is slipping, we set this up as part of the implementations we run for PBSA and BTR operators. Book a 30-minute call via cloudfox.it and we'll map the right navigation for each of your teams — or drop me a message on LinkedIn.