Residents · Staff · Admin · Privacy

Staff aren't aliens: one Habitat account, every hat you wear

Society software usually treats people as one thing: a resident, a guard, an admin. Real people aren’t like that.

  • Priya manages facilities for three societies, and goes home every evening to a flat in a fourth.
  • Rahul is the committee secretary of the society he lives in.
  • Meena runs a property management company and lives nowhere near the buildings she manages.
  • Arjun just moved to the city, has no society yet, and wants to sell his old sofa.

They are all the same kind of person: someone with a life, wearing different hats. On Habitat each of them has one account (their email), and each hat gets the right app.

One account, the right app for each hat

Hat App What it checks
Living in a flat, or just using Habitat Resident app Your flats, in any number of societies; without one, Buy & Sell, Services and Smart Habitat around you
Running a society (committee, office, platform team) Admin web The admin roles you hold in that society
Working in the buildings (facility, MEP and maintenance staff) Staff app Your staff role in the societies you work for

Signing in to each app checks only the roles that app is for. Having an admin role doesn’t change what you see in the resident app, and living in a flat doesn’t open the admin web.

Your home stays your home

Priya’s work never follows her home. In her own society’s resident app she is a resident like everyone else: her flat, her visitors, her bills, her neighbours. The tickets, approvals and staff duties of the societies she works for live in the staff app and the admin web, never in her resident app. Notifications follow the same rule: admin work (approvals, tenancy reviews, tickets for staff) is never pushed to the resident app.

It works the other way too. Her neighbours can’t tell from the resident app that she manages other buildings, and the societies she works for see her as their staff, not as somebody else’s resident.

Admins don’t have to be residents

Meena’s company manages buildings she doesn’t live in, and that’s normal. Her admin role doesn’t come with a flat. She works in the admin web and never needs the resident app for it. The office team, the property manager and Habitat’s own platform team all work the same way.

Committee members who live there: one app is enough

Rahul is the case in between: he lives in the society and helps run it. Asking a committee member to juggle two apps every day is how good volunteers give up. So the resident app shows Rahul one extra thing: Admin view, right under the greeting on his Home. It opens the admin web inside the app, on his society.

Admin view appears only when both are true for the same society:

  1. you live in a flat there (an approved resident), and
  2. you hold an admin role there.

Being an admin somewhere else isn’t enough, and neither is working for Habitat. If Rahul also managed a second society he doesn’t live in, that society would stay in the admin web.

Built to stay separate

  • Separate sessions. Admin view signs in to the admin web with its own session, never the resident app’s. It lasts seven days and can’t be stretched.
  • No extra powers. Admin view can do only what the same person could already do by signing in to the admin web.
  • Never leaves the admin web. Inside Admin view, links to anything else open in the phone’s browser, outside the app.
  • Blocked means blocked. If an account is blocked, every app stops working for it at once.

And Arjun?

Arjun doesn’t belong to any society yet, and Habitat still works for him: he browses Buy & Sell around him, posts his sofa and books a professional. The day he moves into a society, he adds his flat from his profile, and the society’s Home and Community appear in the same app, with the same account.

Staff aren’t aliens. Neither are admins, committee members or people without a society. They are all just people, each with one account and the right app for every hat they wear.