Every entry type looks the same
Guests, workers, delivery people, and contractors need different levels of verification.
Solution - DWAR Gate Access
Gate access with proof in 60 seconds.
Visitor-initiated, 2-minute resident verification for guarded communities.
0+
gate events modeled daily
MyGateNoBrokerHoodApnaComplexWhatsApp BusinessMSG91OpenAPIMyGateNoBrokerHoodApnaComplexWhatsApp BusinessMSG91OpenAPI
DPDP Section 6Consent receipt built inAudit-ready evidence
DWAR is PRAMAAN's gate-console pattern for communities that want faster visitor decisions without weakening privacy. A visitor or service person starts the flow, the resident confirms the purpose, and the gate team receives a simple verification state instead of raw personal documents.
Approvals disappear into chat
Resident approvals are hard to reconstruct after a dispute or incident.
Guards see too much data
Operational staff need a verdict, not a permanent copy of identity documents.
Request to Verify to Audit
One workflow language for every verification decision.
1Scan
Visitor starts with QR or link
The purpose and destination are captured before data is requested.
2Approve
Resident or admin approves the visit
Approval context is recorded with the verification event.
3Admit
Gate team reads current status
The console shows allowed, pending, expired, or review-needed state.
Platform capabilities
Six product blocks built around the buyer's daily work.
intake
Purpose-specific intake
Start every smart gate access (dwar) flow with a named requester, purpose, and consent step.
status
Status-first operations
Show verified, pending, expired, revoked, or review-needed state instead of raw documents.
roles
Role-aware access
Give residents, guards, admins, reviewers, and operators only the view they need.
timeline
Expiry and renewal
Prevent stale verification from silently becoming permanent trust.
audit
Audit packet export
Bundle request, consent, result, timestamp, and reviewer context for later proof.
api
API and dashboard handoff
Operate from the PRAMAAN dashboard first, then connect approved systems through API or webhooks.
DPDP assurance is part of the workflow, not a footer.
Each industry template keeps purpose, consent, masking, residency, and incident posture visible to buyers.
- ✓Purpose-limited consent before processing
- ✓Masked identity display for operational views
- ✓India-region processing posture
- ✓DSR, correction, and grievance routes linked
Township access model
9x
faster status lookup in modeled flow
The gate needed a current status and a resident approval trail, not another register.
Security supervisor
Township operations
Read full case studyIntegration-ready rails
Text marks used where logo licensing is unclear.OpenAPIWebhooksMSG91RazorpayWhatsApp BusinessMicrosoft 365AWS IndiaDashboard exportOpenAPIWebhooksMSG91RazorpayWhatsApp BusinessMicrosoft 365AWS IndiaDashboard export
0x
faster gate lookup in modeled flow
0+
homes covered in reference rollout model
0.97%
uptime posture target for public surfaces
Smart Gate Access (DWAR) FAQ
Related surfaces
Ready to modernise smart gate access (dwar) workflows?
Start with one high-friction workflow, prove the audit trail, then expand across roles.