User Notification channels

[marcinkoziej]

Proca server does not have a UI, so a lot of UI heavy lifting relies on async notification mechanisms:

• email
• automation events (8n8.io, Zapier, etc)

We should do some thinking to decide which notifications should go through which channels. Some need email (because they are email verifications). Some are just for instance admins, and can be brief; some are to users, and preferably should be customizable (email template) to add instruction (eg. You're sync queue to CRM is stuck - what you should do to troubleshoot).

Proca Server notifications

Confirm-able operations (by someone from the organisation - notification reaches all org owners?)

• Partner action page goes live
• (Partner is invited by email to join campaign)
• (Action export is requested)

Confirm-able operations (by individual user)

• User is invited to an organization

Notifications / Verifications used by the auth system (for standalone server, for SSO this is done by SSO identity system)

• Confirm email is real (must be via email)
• Confirm email change to a new email (and verify at same time) (must be via email)
• Password reset

Security notifications (to instance owners and org owners)

• New users created?
• New org created?
• Processing problems (RMQ down, a lot of stuck, queued messages) (instance owners OR org owners)

Security notifications (to individual users)

• New API key created
• New login from IP

[marcinkoziej]

(hold on with this Issue till we sort out the GroupWare on Supabase - perhaps a lot of these notifications will not be necessary for Proca Server any more)