Passport Seva Kendra — Salesforce Platform
A custom Salesforce platform modelling the full Indian-passport application lifecycle — few objects, many fields, clean automation and DPDP-safe PII.
A custom Salesforce platform for a Passport Seva Kendra (PSK) — the offices that process Indian passport applications. It's an independent portfolio project (not affiliated with any government body) built to demonstrate core Salesforce skills end to end: data modelling, automation (Flow + Apex), security/sharing, and integrations (n8n + Twilio + AI).
Design philosophy — few objects, many fields
The whole application lifecycle lives on one object driven by a Status picklist and record types — not a new object per stage. A half-finished form is the same object in Draft status, not a different object.
What exists today
- Object #1 — Passport Application (
Passport_Application__c): ARN auto-number name, OWD Private. - 55 fields across lifecycle, applicant, address, application, payment, verification, consent and derived formulas.
- 6 record types: Fresh, Re-issue, Tatkal, Lost/Damaged, Minor, Diplomatic/Official.
- Dependent picklist (Clearance Level ← Passport Category) and 4 validation rules that enforce on submit while keeping Drafts saveable.
Links
- Code: github.com/imswarnil/Passport-Seva-Kendra-Salesforce
- Org (Developer Edition): passport-seva-kendra-dev-ed.develop.my.salesforce.com
Roadmap: 11 objects total (PSK Office, Slots, Appointments, Documents, Objections, Police Verification, Payments, Renewals, Notification Log, Risk Flags), then a Visa department and Twilio/AI automation.
Advertisement
How I built it
Build log
Open thread
Issues & feedback
Found a bug? Have a feature request? Open an issue below — no GitHub account required, and yes, I actually triage these.
The end. Or is it?
Liked this? There's more where that came from.
I build things like this for fun — and, occasionally, for money.
No projects were harmed in the making of this page.