LCFS - Implement Email Notification Triggers in Backend for Subscribed Users

[AlexZorkin]

Description:

Implement email notification triggers throughout the backend codebase. For example, when a compliance report is assessed, users from the organization that owns the report should receive an email notification if they are subscribed to that notification type. Each notification type should have its trigger implemented at the appropriate location in the backend.

Purpose and benefit to user:

• Keeps users informed about important actions related to them.
• Enhances user engagement and satisfaction.
• Ensures timely communication of relevant events.

Acceptance Criteria:

• [ ] Given I am a user subscribed to a notification type, when the corresponding event occurs (e.g., compliance report is assessed), then I receive an email notification.
• [ ] Given I am a user not subscribed to a notification type, when the event occurs, then I do not receive an email notification.
• [ ] Given the system triggers an event, notifications are sent only to users subscribed to that notification type.

Development Checklist:

• [ ] Identify all notification types and their triggering events.
• [ ] Implement notification triggers at the correct locations in the backend code.
• [ ] Ensure notifications respect user subscription preferences.
• [ ] Integrate triggers with the existing email templates.
• [ ] Test to confirm that notifications are sent correctly to subscribed users.

Notes:

• Coordinate with the business team to verify notification requirements.
• Handle user data securely when sending emails.
• Ensure that adding new notification types in the future is straightforward.

[airinggov]

ANALYST Transfers Submitted to government for analyst review

• SUBMITTED (Signed and submitted by transfer partner 2)

Rescinded by either transfer partner

• RESCINDED (this should only trigger if the report was previously Submitted but not Sent)

Director recorded/refused

• RECORDED or REFUSED

Initiative agreements and other transactions Director approved/returned to analyst

• APPROVED or RETURNED (initiative agreements, designated actions, admin adjustments)

Compliance & supplemental reports Submitted to government for analyst review (or returned by compliance manager)

• SUBMITTED (both compliance and supplemental reports)

Returned or recommended by compliance manager

• RECOMMENDED BY MANAGER or SUBMITTED (compliance, supplemental and reassessment reports)

Director assessment

• ASSESSED or REASSESSED (compliance, supplemental and reassessment reports)

COMPLIANCE MANAGER Compliance & supplemental reports Submitted to government for analyst review

• SUBMITTED (both compliance and supplemental reports)

Analyst recommendation (or returned by the director)

• RECOMMENDED BY ANALYST (compliance, supplemental and reassessment reports)

Director assessment

• ASSESSED or REASSESSED (compliance, supplemental and reassessment reports)

DIRECTOR Transfers Analyst recommendation

• RECOMMENDED

Initiative agreements and other transactions Analyst recommendation

• RECOMMENDED (initiative agreements, admin adjustments)

Compliance & supplemental reports Compliance manager recommendation

• RECOMMENDED BY MANAGER (compliance, supplemental and reassessment reports)

BCEID Transfers Transfer partner proposed, declined, rescinded or signed & submitted

• SENT or DECLINED or RESCINDED or SUBMITTED (by transfer partner/other BCeID organization)

Director recorded/refused

• RECORDED or REFUSED

Initiative agreements and other transactions Director approved

• APPROVED (initiative agreements, admin adjustments)

Compliance & supplemental reports Director assessment

• ASSESSED or REASSESSED (compliance, supplemental and reassessment reports)