Design feedback wanted: Employee self-enrollment and account provisioning for Frappe HR

I’m considering the next feature for frappe_hr_self_service: employee self-enrollment leading into first login.

The interesting part is that organizations may already have partial data:

  • neither Employee nor User exists
  • Employee exists, but User does not
  • User exists, but Employee does not
  • both exist but are not linked
  • both already exist and are linked
  • existing records conflict or are ambiguous

Rather than treating this as simple “self-registration”, I’m proposing a staged flow:

HR invitation
    ↓
Employee registration
    ↓
HR review
    ↓
Reconcile existing Employee/User records
    ↓
Create or link only what is missing
    ↓
First login

Ambiguous cases would stop for HR review rather than automatically creating or relinking records.

I’ve written up the proposed state matrix, trust boundary and first milestone in GitHub Issue #6:

Employee self-enrollment and account provisioning

I’d particularly appreciate feedback from people who have implemented something similar:

  1. How are you currently handling Employee ↔ User provisioning and reconciliation?
  2. Are there existing Frappe/HRMS mechanisms we should reuse instead of building new ones?
  3. Would an invitation-based flow be useful in your deployments, or do you generally need completely open self-registration?

Feedback on edge cases we haven’t considered would be especially useful.

Reviving this thread because our team is currently tackling this exact onboarding challenge. Did the core team make any headway on integrating Microsoft 365 or Google Workspace for automated email provisioning? Also, I would love to know how others handle document rejection loops without completely stalling the process. Any updates from recent releases or custom setups would be super helpful.