Enhancements to the Vulcan Notification System

[vanessuniq]

Background

Vulcan currently supports notifications via Email and Slack:

Email notifications are centered around reviews:

• Emails are sent to project admins CC’ing the user requesting a review.
• Users receive an email when a request is approved, revoked, or when more changes are requested.

Slack notifications currently support:

• Project creation, removal, & renaming
• Component creation and removal
• SRG upload & removal
• Assigning & removing Vulcan admin
• Adding/removing member from a project or component
• Updating member role

Currently, a single private channel can be set in the app configuration for Slack notifications.

The goal is to enhance the current system and extend notifications to Teams and SMS.

Tasks

1. Extend Notification Support

• Implement Teams notifications
• Implement SMS notifications

2. Enhance Slack Notification Use Cases

• Enable users (admins) to provide the Slack channel they want to use for each project or component. This can be provided on project/component creation or edited in the project/component metadata. #591
• Enable users to provide their own Slack user ID if they would like to receive Slack DMs (e.g. when added/removed from a project, role changes, review requests, etc). #592

3. Update Email Notification Use Cases

• Extend email notifications to alert users when their role changes. #593

4. User Notification Settings

• Implement user notification settings to allow users to set their preferred notification method (direct email, Slack, Teams, SMS).

5. Define Notification Triggers

• Define and implement when notifications should be triggered at the project, component, or user level.