How Habitat's gate works: visitors, codes and exits
Habitat accounts for every visitor from the gate until they leave, and it shows the society office the exits the guard missed. Most gate apps stop at “let them in”. Habitat also records how many people came, who left and when, and flags anyone still marked inside.
- Every entry has an approval behind it: the resident’s tap, a pre-approval code, a call to the flat, or the guard’s own decision, with the name of the person who gave it.
- Every exit is recorded, for the whole group or part of it, with the time and who recorded it.
- Missed exits don’t disappear. They are closed automatically or confirmed by the household, and always flagged “exit not recorded by the guard”.
How a visitor gets in
There are four ways in:
- A pre-approval code the resident shared, entered by the guard.
- The resident taps Allow on their phone when the guard logs the visitor.
- The guard calls the flat when nobody answers in the app.
- The guard lets them in on their own responsibility, recorded as such.
If the resident taps Deny, the visitor is turned away. For deliveries, the resident can ask the guard to keep the parcel at the gate.
Pre-approval codes
A code works only inside the time window the resident chose, as many times as needed, for one visit at a time.
| Choice | Window |
|---|---|
| Next few hours | 4 hours for guests, 2 for deliveries, cabs and services |
| Rest of today | Until 11:59 pm |
| Tomorrow | All of tomorrow |
| Several days | 2 to 31 days, ending 11:59 pm on the last day |
The app shows the exact end time before the code is made. After that time the guest needs a new code or the resident’s approval at the gate. The resident can extend a code at any time (up to 31 days from its start) or cancel it.
At the gate, the guard types the 6-digit code:
- Inside the window: checked in.
- Too early: “Valid from Tue 4 Nov, 6:00 pm”.
- Too late: “Expired at 8:00 pm”.
- Cancelled: “Cancelled by the resident”.
When a code can’t be used, Ask the flat instead turns it into a normal approval request with the name and flat filled in.
Families and groups
The guard counts people at the gate; residents never have to guess how many are coming. One code covers a whole family or group.
- At every check-in the guard sets People coming in (it starts at 1).
- Latecomers are added to the same visit with Add people.
- If the group is already inside on that code, the guard sees “Already inside since 10:42 · 4 people”, so one code can’t open a second visit by mistake.
Leaving
The guard checks visitors out as they leave: the whole group with one tap, or some of them. If 2 of 4 leave, the visit stays open with 2 inside. Every coming and going is kept:
| Time | What happened | Recorded by |
|---|---|---|
| 10:42 | 3 came in | Guard |
| 11:05 | 1 more came in | Guard |
| 14:30 | 2 left | Guard |
| 16:10 | 2 left | Guard |
Residents get a quiet notification when their guests leave. Deliveries and cabs don’t trigger one.
When the guard forgets to check someone out
Each society chooses what happens, per type of visitor.
Visitors let in without a code are checked out automatically after a set time. Auto exit is switched on or off for each type of visitor, each with its own time; the defaults are below.
| Visitor | Auto exit after |
|---|---|
| Guests | 12 hours |
| Cabs | 1 hour |
| Deliveries | 1 hour |
| Services | 4 hours |
For a type with auto checkout switched off, the household is asked when that time runs out, and again after the same time if they answer “Still here”.
Visitors on a code, when the code ends:
- Clear after expiry (the default for cabs, deliveries and services): checked out automatically.
- Ask residents (the default for guests): the household gets one notification and reviews it in their visitor log. They’ve left closes the visit; Still here extends the code.
Every exit made this way is flagged “exit not recorded by the guard”: closed automatically, confirmed by the resident, or marked by the office. Nothing is hidden, and nobody’s home screen is crowded with reminders.
Who sees what
| Resident app | Guard app | Society office | |
|---|---|---|---|
| Arrivals | Allow / Deny, or “has arrived” for codes | Waiting list and check-in | Live log from every gate |
| Group size | In the alert and the log | Set at check-in | On every visit |
| Who approved | Name and how | On the visit | Name, how and when |
| Exits | Quiet notice, times in the log | Check out all or some | Every exit with its guard |
| Missed exits | To review in the visitor log | Shown first in amber | Flagged on every visit |
Quick answers
| Situation | What happens |
|---|---|
| Guest arrives after the code ended | “Expired at 8:00 pm”; the guard asks the flat |
| Same code again while the group is inside | The guard adds people or checks them out; no second visit |
| Guest goes out and comes back in the window | Checked out, then in again on the same code |
| A relative stays a week | The resident picks Several days, or extends the code |
| A cab driver is never checked out | Checked out after 1 hour, flagged as auto exit |
| A guest on a code stays past it | The household is asked once and reviews it in the visitor log |