- Professional associations that need to verify credentials or qualifications
- Organizations handling sensitive activities (working with children, financial services)
- Regulatory requirements for member identification
- Any situation where you need to confirm someone’s real identity
- Casual communities, hobby groups, or social clubs where identity verification is overkill
How to enable
Settings → Modules → Identity Validation| Setting | What it does |
|---|---|
| Require ID validation | Make identity verification mandatory for all members |
| Accepted document types | Choose which documents you accept: national ID, passport, driver’s license, residence permit |
| Require selfie | Members must take a selfie that’s compared against their document photo |
| Auto-expire reminder | Days before document expiry to notify the member (e.g., 30 days) |
What the member does
Path: Profile → Identity Documents
Upload document
Member uploads photos of the front and back of their ID document (national ID, passport, or driver’s license).
Review OCR data
The system automatically extracts data from the document: name, date of birth, document number, expiry date. The member reviews and corrects any OCR errors.
What OCR extracts
| Field | Source |
|---|---|
| First name, Last name | From the document |
| Date of birth | From the document |
| Document number | ID or passport number |
| Expiry date | Document expiration |
| Address | If present on the document |
What the admin does
Review queue
Admins see pending verifications in their review queue. Each entry shows the member’s name, submission date, document type, and status.Verification process
When reviewing a submission:- Check the document — Is it clear, readable, and appears authentic?
- Compare photos — Does the profile photo match the document photo?
- Review extracted data — Does the OCR data match what’s visible on the document?
- Take action:
| Action | When to use |
|---|---|
| Approve | Document is valid, photos match, data is correct. Member gets a verified badge. |
| Reject | Document is invalid, expired, or photos don’t match. Provide a reason — the member can resubmit. |
| Request resubmit | Images are blurry or partially obscured. Asks for better quality without rejecting outright. |
Verification statuses
| Status | What it means |
|---|---|
| Not submitted | Member hasn’t uploaded documents yet |
| Pending | Submitted, awaiting admin review |
| Verified | Identity confirmed — badge displayed on profile |
| Rejected | Verification failed — member can resubmit |
| Expired | Document has passed its expiry date — member needs to resubmit |
Combining with adhesion
For maximum vetting, combine identity validation with Adhesion:- Applicant submits a membership application (adhesion)
- As part of the application, they upload identity documents
- OCR pre-fills form fields from the document data
- Admin verifies identity as part of the application review
- Approval confirms both the application and the identity
Document expiry management
When you set an auto-expire reminder (e.g., 30 days), the system:- Tracks document expiry dates
- Sends reminders to members before expiry
- Changes status to Expired when the document expires
- The member must upload a new document to regain verified status
Privacy and security
- Uploaded documents are encrypted at rest
- Access is restricted to administrators only
- You can configure retention policies (delete after verification, keep for X months/years, or manual deletion only)
- Members can delete their own documents from their profile
Common scenarios
A member's verification was rejected — what should I tell them?
A member's verification was rejected — what should I tell them?
When rejecting, provide a clear reason: “Document expired”, “Photo doesn’t match profile”, “Image too blurry to read”. The member receives a notification with your reason and can resubmit. Specific feedback prevents repeated failures.
OCR extracted the wrong name from a document
OCR extracted the wrong name from a document
OCR isn’t perfect, especially with non-Latin scripts or damaged documents. The member can correct OCR errors before submitting. If they missed an error, reject with “Name doesn’t match document” and ask them to resubmit with corrected data.
Should I require selfies?
Should I require selfies?
Require selfies if you need to verify that the person uploading the document is actually the person on the document. Skip it for lower-stakes verification where the document itself is sufficient (e.g., confirming they have a valid professional license, regardless of who uploaded it).
A member's document expired — do they lose access?
A member's document expired — do they lose access?
That depends on your configuration. If identity validation is mandatory, an expired document may restrict their access until they resubmit. If it’s optional, expiry just removes the verified badge but doesn’t affect access.
Technical requirements
- OCR processing: Requires AWS Lambda configuration
- Document storage: AWS S3 for uploaded files
- Both are part of the standard Orgo cloud setup — no additional services needed.
Related
- Adhesion — Combine identity verification with membership applications
- Profile Fields — Additional member data
- Privacy Settings — Data visibility controls