FAQ: society visitor & gate
What is visitor & gate on Plinth? Residents pre-approve visitors with OTP + QR passes; guards verify at Gate desk; walk-ins ping flat owners for approve/deny; entry and exit are logged.
How do I create a visitor pass? Open Visitors (/visitors), choose a visit kind, enter
visitor details, and submit. create_pass returns a 6-digit OTP and QR code.
How long is a pre-approved pass valid? 24 hours from creation (default p_valid_hours).
What visit kinds are supported? guest, delivery, cab, vendor, staff, and other.
Who can use Gate desk? Society admins and society staff (guards) at /admin/gate.
How does guard verification work? Enter the visitor OTP (verify_pass) or scan the
QR (verify_pass_qr). Valid expected passes move to approved.
What is a walk-in? Someone arrives without a pre-approved pass. Guard logs them via
request_walkin_approval — flat owners get a notification and approve (approve_visit) or deny
(deny_visit).
How is entry and exit recorded? Guard taps Log entry or Log exit on Gate desk —
log_gate_event writes to gate_events and updates pass status to entered or exited.
Can I revoke a pass I created? Yes — residents can cancel an unused pass from Visitors before the visitor arrives.
Do tenants use the same flow? Walk-in approval goes to flat owners on the roster. Tenant access depends on your society's claim model — flat owners receive approval pings.
What tier is visitor & gate on? Operations — see pricing.
Is every gate action audited? Yes — pass creation, verification, approval, denial, entry, and exit append to the audit log and gate_events.