
Quick Answer: Pre-approve the guest. In the DoorVi app, add the visitor's name and date, pick a pass (single-use, date range, recurring or event) and share the code. At the gate, the guest scans the QR code, types the code and walks in, and the entry is logged as pre-approved. Unexpected visitors still video-call you as usual.
DoorVi, a QR-code video intercom and visitor management platform, uses pre-approval alongside its normal video-call entry. The rest of this guide covers which pass to use, what each person sees, and when a different setup fits better.
Picture a normal week: the plumber on Tuesday morning, your sister staying Friday to Sunday, the cleaner every Tuesday, and a birthday dinner on Saturday. Each of those visits is known in advance, yet with a classic intercom every one of them means a call, often in the middle of a meeting, and a guest waiting at the gate if you miss it.
Visitor pre-approval moves that decision earlier. You approve the visit once, when it's convenient, and the guest gets in on arrival without anyone answering anything.
| Pass type | What it does | Typical use |
|---|---|---|
| Single-use | Valid for one entry | A plumber, a technician, a one-off guest |
| Date range | Valid between two dates | Family staying for a weekend |
| Recurring | Valid on a repeating schedule | A cleaner every Tuesday, a tutor twice a week |
| Event | One pass shared by a guest list | A birthday party, a meeting, a community event |
For couriers there's a dedicated flow that uses the parcel's tracking number instead of a code: see delivery pre-approval.
Using pre-approval in an office building without a front desk
Before: answers the intercom for every visitor, or leaves names with a doorman who may not be on shift.
After: creates a pass in the DoorVi app in under a minute, shares the code, and gets on with the day. Every entry shows up in the history, marked pre-approved.
Before: waits at the gate while the intercom rings, or calls the resident's mobile.
After: scans the DoorVi QR code with their phone camera, types the code, and walks in. They don't install an app and don't see the resident's phone number.
In the Guard + QR entry mode, the guard keeps using the Guard Doorman app for visitors who need help, while pre-approved guests let themselves in. In QR-only mode, there's no guard at all.
Sets the entry mode for each entrance in the admin dashboard (multi.doorvi.co), uploads residents by CSV, and connects the lock. The visitor log shows who was expected and who actually arrived, which is a clean audit trail for the building. Setup follows the property setup guide, and residents can use the residents' guide.
Nothing changes for them. They scan the same QR code and video-call the resident, who sees them and opens the gate remotely from their phone. Pre-approval just removes the call for the visits you already knew about.
Pre-approval is a gate automation feature, so the entrance needs a lock DoorVi can release: an electric strike or maglock on a relay (ESP32, Sonoff, Tasmota or Waveshare), or an existing ProdataKey (PDK) or Brivo access-control door. See relays, PDK and Brivo.
No. The guest scans the QR code at the gate with their phone camera and types the code in the web page that opens.
Yes. Use a recurring pass, for example for a cleaner every Tuesday.
Yes. An event pass is shared by all the guests on the list for that event.
Yes. The visit appears in the history with the time and the apartment, marked as pre-approved.
They scan the QR code and video-call the resident, who can open the gate remotely.
No, not unless you turn on the "Callback Number" option.
DoorVi's support team resolves support tickets within 24 hours.
Watch the 1-minute visitor pre-approval demo, then book a 15-minute demo. DoorVi's support team resolves support tickets within 24 hours.
About the author: Sachin Gupta is a Director at DoorVi and works on QR video intercom and access-control deployments for condomínios, apartment buildings and offices in Brazil, the US and India.
By Sachin Gupta, Director, DoorVi · Published 27 September 2026 · Last updated: 3 October 2026