Before arrival
A resident registers an expected guest, delivery or service visit for their unit.
shield_lock VISITORS & SECURITY
For residents and guards
A clearer visitor journey from invite to arrival.
Residents share visit details before a guest arrives. Guards review expected visitors, record entry and exit, and keep a gate history that authorised community staff can follow.
person_add Resident pre-approval
login Guard check-in
history Gate history
qr_code_scanner
CHECK-IN
Guard check-in view
Expected visits and arrival records
THE VISITOR JOURNEY
Three steps. One shared record.
The resident, guard and admin each see the part of the visit relevant to their role.
At the gate
A guard reviews the visit in the guard workspace and records the check-in.
On departure
Check-out closes the visit, leaving an entry and exit history for authorised staff.
ROLE-BASED WORKSPACES
Clear tasks for everyone at the gate.
The visitor workflow connects the unit, the gate and the community office without a separate paper register.
Explore security on the platform tour arrow_forwardhome
Residents
Share expected visit details for the right unit before the visitor reaches the gate.
security
Security guards
Use a focused guard view to review arrivals, record entry and record exit.
admin_panel_settings
Community administrators
Review gate activity and visitor records within the community's role permissions.
COMMON QUESTIONS
Visitors & Security FAQs
Can residents register deliveries?
Yes. Expected visits can include guests, deliveries and service people.
Who records arrival and departure?
The security guard uses the guard workspace to record check-in and check-out.
Can an admin review previous visits?
Authorised community staff can review the gate history associated with their community.
Where does a resident start?
A resident chooses the relevant property and adds the expected visitor details.
See the visitor journey for your community.
Tell us about your gate process, resident roles and the details your guards need.