The whole portfolio. One screen.
The operator console runs access, residents, visitors, amenities, rent and analytics across every site, signed in with Microsoft Entra, with every action landing on one audit trail.
Already a customer? Sign inRunning in pilot today. What we demo is what is running.
Every site. Every module. One sign-in.
A live event feed
Door events, visitor passes, bookings and payments land in one feed as they happen, across every site. The console shows the building as it is, not as of last night's export.
The numbers at a glance
Occupancy, arrears and doors online sit on the home view, and anything that needs attention is one click from the figure to the record behind it.
The module rail
Access, residents, visitors, amenities, payments and analytics are one navigation, not six portals. Same record, same sign-in, no swivel-chair work.
Entra sign-in, role-scoped views
Teams sign in with the Microsoft accounts they already have. A concierge sees their building; an operator sees the portfolio. Scope is a role, not a habit.
Every action on the trail
Everything the console can do is a governed tool. Issue a credential, confirm a booking or raise a notice and the action lands on one immutable audit trail, attributed to you.
One platform. Not a product bundle.
The console is not an admin panel bolted onto a database. It is a view over the same governed tool surface the API exposes and Sentinel will run, which is why what you see in a demo is what actually runs.
The portfolio view lives here
Occupancy, arrears and usage across every site, with every number resolving to the trail.
ExploreResidents act on the same record
What a resident does in the app lands in the console feed the moment it happens.
ExploreThe agent works the same tools
Sentinel is coming up on the exact tool surface the console runs, so nothing it does is invisible.
ExploreA view over governed tools, not a backdoor.
There is no console-only path around the rules. Every button in the console calls the same role-scoped tools as the API, under Microsoft Entra identity, and every action is written to one immutable audit trail with Australian data residency. If your role cannot do something, the console cannot either.
Is this another portal to add to the pile?
The opposite: the console replaces the pile. Access, residents, visitors, amenities, rent and analytics run in one place, so the portal count goes down, not up.
See the console on your portfolio.
One screen over access, residents, rent and analytics, running in pilot today. Book a pilot and put a real building on it.
Prefer email? hello@ark360.com.au