Enhance portal profile/support modules and add rebuild prompt doc
Add profile (verify-to-reveal, KYC rules, contact-change OTP flows, notifications/consent tabs, devices) and support (5 channels, message center, ticket routing, live chat, help center) updates, the geo BFF route, login auth flow, and a self-contained module rebuild prompt. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,38 @@
|
||||
# YEIDA Portal — Consent Options (for review)
|
||||
|
||||
Prepared as the meeting action item. **Consent** governs *what may be collected, disclosed or processed*. **Notification** governs *how we reach you* (email / SMS / WhatsApp / call / post) — these are separate and live under Profile → Notifications & Privacy.
|
||||
|
||||
## A. Individual consent options (toggles)
|
||||
|
||||
| # | Consent | Default | Locked? | What it controls |
|
||||
|---|---------|---------|---------|------------------|
|
||||
| 1 | **Data Processing** (statutory) | ON | 🔒 Yes | Administer the allotment, payments & statutory notices. Required by law — cannot be turned off. |
|
||||
| 2 | **Profile Visibility to Authority Officers** | ON | No | Show your name & plot to the officers handling your case. |
|
||||
| 3 | **Analytics & Preference Cookies** | OFF | No | Usage analytics to improve the portal. |
|
||||
| 4 | **Empanelled Partner Sharing** | OFF | No | Share with empanelled service partners (contractors, banks) for services you request. |
|
||||
| 5 | **Identity Disclosure for Transfers** | OFF | No | Disclose allotment identity to a prospective buyer during a plot transfer. |
|
||||
| 6 | **KYC / Document Sharing** | ON | No | Share KYC docs with authority cells for verification (needed to complete KYC). |
|
||||
| 7 | **Cross-border Data Transfer (NRI)** | OFF | No | Process data for an overseas account holder / allottee. |
|
||||
| 8 | **Marketing Communications** | OFF | No | Newsletter / promotions / product updates (granular per type). |
|
||||
|
||||
## B. Dummy consent levels (tiered variant — for the dropdown demo)
|
||||
|
||||
A single selector that bundles the toggles above, for users who prefer one choice:
|
||||
|
||||
- **Level 0 — Essential only**: #1 only. Everything else OFF.
|
||||
- **Level 1 — Standard**: Essential + #2 (officer visibility) + #6 (KYC sharing).
|
||||
- **Level 2 — Enhanced**: Standard + #3 (analytics) + product updates.
|
||||
- **Level 3 — Full**: Enhanced + #4 (partner sharing) + #5 (transfer disclosure) + #8 (marketing).
|
||||
|
||||
Selecting a level pre-sets the individual toggles; the user can still fine-tune any toggle afterwards (level becomes "Custom").
|
||||
|
||||
## C. Consent vs Notification (kept separate)
|
||||
|
||||
- **Consent** → the table above (governance / disclosure control).
|
||||
- **Notification** → delivery channels per contact (primary/secondary email & phone): Email, SMS, WhatsApp, Call, Post — plus preferred time window & timezone. At least one channel always stays enabled.
|
||||
|
||||
## Open items for next meeting
|
||||
- Confirm the final consent labels & defaults.
|
||||
- Decide: tiered levels (Section B) **and** granular toggles (Section A), or granular only.
|
||||
- Confirm which consents are statutory/locked vs user-controllable.
|
||||
- Source of truth: pull existing consent from the authority platform vs portal-managed.
|
||||
Reference in New Issue
Block a user