-
Notifications
You must be signed in to change notification settings - Fork 19
Labels
BackendBackend Related IssueBackend Related IssueFrontendFrontend Related IssueFrontend Related IssueNew FeatureNew feature to be implementedNew feature to be implementedRefactorCode ImprovementCode Improvement⚡ImportantHigh-impact issue that needs to be resolved before the next releaseHigh-impact issue that needs to be resolved before the next release
Milestone
Description
📋 Overview
Implement a robust, provider-agnostic email notification system for both authentication and future transactional use cases (e.g., team invites, document views). The system must support multiple providers and be configurable through environment variables.
This initiative is broken into four sub-issues, starting from provider evaluation and ending with real-world email flows like document share alerts.
🧩 Sub-Issues
- Research & Select Email Provider #275
- Configure Email Credentials & Environment Setup #276
- Create Core Email Service Layer & Integrate Auth Email Flows #277
- Add Support for Non-Auth Notification Emails #278
🔄 Guidelines
- Code should use a shared
emailServiceabstraction — no direct provider usage in feature logic. - Email sending must be disabled by default in local/dev environments unless explicitly enabled.
- All templates must support dynamic values, fallback gracefully, and log failures.
- All implementation should align with modular design and Next.js 15 best practices.
Sub-issues
Metadata
Metadata
Assignees
Labels
BackendBackend Related IssueBackend Related IssueFrontendFrontend Related IssueFrontend Related IssueNew FeatureNew feature to be implementedNew feature to be implementedRefactorCode ImprovementCode Improvement⚡ImportantHigh-impact issue that needs to be resolved before the next releaseHigh-impact issue that needs to be resolved before the next release