A modern development is rarely just one building. Take a complex like Discovery Point: Building A, Building B, Building C — several buildings on one site, sharing the same grounds, and sharing amenities like the pool and gym that every resident can use. Often each building is its own body corporate. That shared access is exactly what makes it a complex rather than a row of unrelated buildings.
If you manage a complex like that, you already know the routine older software forces on you. To look at another building, you switch accounts — and you only ever see one building at a time. Answering a simple whole-complex question (“which buildings have overdue maintenance right now?”) means switching, looking, switching again, and holding the picture together in your head.
ComtyLink takes a different approach: one account for the whole complex. Every building is there together, in one place — nothing to switch between, no “active building” to pick. You see and manage the entire complex at once, while each building’s residents stay separate and the shared amenities stay open to everyone.
The Problem With Switching Between Buildings
Most platforms assume one building, one body corporate. When you manage a complex of several buildings, they make you handle each one as a separate context — usually you can switch within a single login, but you still switch accounts, and you only ever see one building at a time. That design creates three everyday headaches:
Constant switching. Every time you move between buildings, you change context and wait for the next one to load. Across a complex of three or four buildings, that’s a meaningful chunk of your day spent just navigating, not managing.
No whole-complex view. Because you only ever see one building at a time, there’s no single place to ask “how is the complex doing?” You have to look at each building one by one and hold the picture in your head.
Shared amenities don’t fit. A complex has a shared pool, gym, or BBQ area that every resident is entitled to use. When the software treats each building as a separate island, those shared spaces become awkward to set up and manage.
For anyone running a multi-building complex, this is one of the most common complaints about older platforms.
How ComtyLink Handles It
In ComtyLink, your one account holds the whole complex. There’s no “active building” to set before you can act, and nothing to switch between. Every building in the complex is right there at once.
Everything in one place. You don’t jump between buildings — you see them together. Every building is in the same account, side by side, so managing the complex feels like managing one thing, not several.
The whole complex at a glance. Your dashboard shows what needs attention across every building: where the open maintenance jobs are, which buildings have pending bookings or sign-ups waiting. You spot the building that needs you before you go digging.
Shared amenities built in. The pool, the gym, the BBQ area — they belong to the complex, so every resident from every building can book and use them. The shared access that makes it a complex is handled natively, not bolted on.
This is the difference between software designed for a building and software designed for a complex — a development that’s really several buildings sharing a site, run as one.
Each Building Stays Its Own — Shared Spaces Stay Shared
Here’s the balance that matters, and it’s worth being precise about: managing the whole complex from one account does not mean the buildings are merged.
Each building keeps its own residents, notices, documents, and records. A resident in Building A sees only Building A’s notices and Building A’s documents — and has no visibility into Building B or C. The fact that you, the manager, can see all of them from one account changes nothing for them. From a resident’s point of view, their building is their building.
But the shared amenities are exactly that — shared. The complex pool and gym are open to every resident, from every building, because that shared access is what a complex is. ComtyLink keeps the two things straight: each building’s own data stays within that building, while the amenities that belong to the whole site are available to everyone.
That gives you a clean split:
- Residents see their own building’s residents, requests, and notices — and can book the shared amenities the complex offers.
- Building managers see only the buildings they’re assigned to. You can run the whole complex, or hand a manager just the buildings they’re responsible for.
- Each body corporate keeps its own records and history — distinct from every other building in the complex.
So you get the convenience of running the complex as one and the right separation between buildings, with shared spaces shared. There’s no trade-off between the two.
Why This Matters for Multi-Building Complexes
If you look after a single, standalone building, a one-building login is fine. But a lot of modern developments aren’t single buildings — they’re complexes: several buildings on one site, sharing grounds and amenities, often with a separate body corporate each. Most platforms quietly assume one building and make a multi-building complex feel like several disconnected jobs.
ComtyLink is built the other way around. The complex is the unit. Whether your site is two buildings or six, you run it from one account — every building together, each one’s residents kept separate, and the shared amenities open to all.
For strata managers in particular, this means you can hand a building manager access to exactly the buildings they handle — no more, no less — and know that the boundary is enforced for you, not left to discipline and good intentions.
See It for Yourself
ComtyLink offers a free 3-month trial with full access to every feature — and free data migration if you’re moving from another platform. If you manage a multi-building complex and you’re tired of switching accounts, this is the difference you’ll feel on day one.
Get in touch and we’ll walk through how it would work for your complex. You can also read more about managing a multi-building complex in ComtyLink. Or, if you’re currently on MYBOS, see our migration guide and the side-by-side comparison.
Related reading: