How Visitor & Gate Works in Plinth (Step by Step)

How visitor & gate works in Plinth

Residents pre-approve visitors with OTP, QR, and invite links. Guards verify at Gate desk with camera scan or OTP. Walk-ins notify flat owners; deliveries support Leave at Gate parcels. Every transition is audit-logged.

Flow A: Pre-approved visitor pass

Step 1: Resident creates a pass

1. Open Visitors (/visitors).
2. Tap Pre-approve — choose kind: guest, delivery, cab, vendor, staff, or other.
3. Enter name, optional phone, company (delivery presets), vehicle, and optional valid from time.
4. Save as recurring visitor template for frequent staff or vendors.
5. Submit — create_pass returns OTP, QR, and an invite link (/invite/gate/:token).

Step 2: Guard verifies at gate

1. Open Gate desk (/admin/gate).
2. Scan QR with the camera or enter the 6-digit OTP.
3. verify_pass / verify_pass_qr approves expected passes and records verification.

Step 3: Log entry and exit

1. Tap Entry — log_gate_event; flat owners get an entry notification.
2. Tap Exit when they leave.
3. Use Inside now tab to see who is on campus. Multi-gate societies pick the active gate.

Flow B: Walk-in approval

1. Guard logs walk-in with flat, kind, phone (lookup returning visitors), vehicle, and optional photo.
2. Flat owners approve, deny, or Leave at gate (deliveries).
3. Guard marks parcel collected → resident gets pickup OTP → guard confirms handover.

Offline and export

• Entry/exit queues locally when offline; sync when connectivity returns.
• Admins export gate events CSV from the passes tab.

Resident guide · Gate desk guide · FAQ.