[Exploratory] Dynamic email verification configuration

[heysamtexas]

Description

EXPLORATORY TICKET - Research making django-allauth email verification settings dynamic through admin interface.

⚠️ Complexity Warning: This may require adapter overrides and could introduce significant complexity. Research thoroughly before implementation.

Current State

Email verification settings are hardcoded in settings.py:

• ACCOUNT_EMAIL_VERIFICATION = "mandatory" (or similar)
• ACCOUNT_EMAIL_VERIFICATION_BY_CODE_ENABLED = False

Research Goals

• Investigate if allauth adapters can read from database configuration
• Test performance impact of dynamic config lookups
• Assess complexity vs benefit ratio
• Document any limitations or edge cases

Potential Implementation

Add fields to SiteConfiguration:

• email_verification_required - Boolean for mandatory verification
• email_verification_by_code - Toggle code vs link verification

Questions to Answer

1. Can adapter methods safely override these settings?
2. What's the performance impact on every request?
3. Are there caching strategies that make this viable?
4. Do settings changes require server restarts?

Decision Criteria

• Low complexity implementation path exists
• Performance impact is negligible
• Clear benefit to admin users

Labels: research, django-allauth, complexity-warning
Priority: Low (Research only)