- PRAMAAN is not a resident-surveillance layer.
- Consent is required.
- Design for role-based access and minimum visibility.
- Do not forward raw documents.
- Use DSR and grievance routes for disputes.
Overview
Worker onboarding
Use consented checks and badges for repeat worker trust workflows.
Visitor day pass
Keep visitor checks purpose-limited and retention-aware.
Vendor access
Separate vendor onboarding from resident or visitor workflows.
Resident request
Use clear purpose and consent; do not run secret resident checks.
Renewal
Refresh signals when validity or role requirements change.
Dispute/correction
Route wrong or stale data through PRAMAAN correction or DSR paths.
What to do
- 1Define the workflow and purpose.
- 2Collect consent through the guided flow.
- 3Give committee members only the access their role needs.
- 4Route corrections, disputes, and grievances properly.
Role-based access module
Treat these as design roles unless your current PRAMAAN workspace explicitly enables the exact permissions. The product should minimize what each role can see.
Committee admin
Reviews policy, onboarding, and escalations.
Security desk
Needs operational status, not raw documents.
Vendor coordinator
Manages vendor-specific workflow and renewals.
Resident
Sees requests and relevant status where permitted.
Worker
Owns badge sharing, correction, and renewal paths.
What to avoid
- Do not use PRAMAAN for resident surveillance.
- Do not run checks without consent.
- Do not forward raw documents in committee groups.
- Do not describe PRAMAAN as a police-verification replacement.
Frequently asked questions
Who is this for?›
RWA committees, facility managers, security supervisors, and society admins coordinating worker, visitor, vendor, and resident verification.
Can a society run checks without consent?›
No. PRAMAAN workflows are consent-first and should state a clear purpose.
What can be verified?›
Use the minimum checks needed for the role and purpose, such as identity, phone, address, badge status, or source-backed risk signals where lawful and supported.
How should visitor logs be handled?›
Visitor logs need purpose, access limits, and retention discipline. Avoid turning logs into surveillance records.
Can committee members see raw documents?›
Committee workflows should rely on permitted status signals and audit trails. Raw document access should be tightly controlled where supported.
Is this a police verification replacement?›
No. PRAMAAN provides source-backed verification signals and workflows; it should not be described as a police replacement or legal guarantee.
Glossary terms
When to talk to a human
Use human handoff for society rollout, unclear disputes, sensitive resident cases, or procurement questions.
Use formal routes for data rights
Access, correction, erasure, nomination, consent withdrawal, and grievance requests should use DSR, DPO, or grievance pages so scope and handling are tracked.
Was this helpful?
Feedback helps PRAMAAN improve support answers without collecting raw identity data.
Move safely from answer to action
Use the route that matches the sensitivity of your case. Keep raw documents out of support messages unless a controlled workflow asks for them.