# InApp Notification Syncing

## Should has inApp Templates:
- review_submit:
- Email status: It sends email notification to buyer RFQ owner
- inApp Status: So Should I send inApp notification to RFQ owner too?
- inApp template: Hello {{rfqOwner}}, A review was submitted to RFQ {{RFQ_REF}}, {{RFQ LINK}}

- request_access_basic_p:
- request_access_premium_p:
- Email status: It sends email notification to all supplier users when get access
- inApp Status: So Should I send inApp notification to all supplier users when get access too?
- inApp template: Hello {{supplierName}}, You got access to RFQ: {{RFQ_REF}}, {{RFQ LINK}}

- auction_assigned:
- Email status: It sends email notification to winner supplier user
- inApp Status: So Should I send inApp notification to winner supplier user?
- inApp template: Hello {{supplierName}}, You won Auction: {{Auction_REF}}, {{AUCTION LINK}}

- lose_auction_inside:
- Email status: It sends email notification to loser supplier users
- inApp Status: So Should I send inApp notification to loser supplier users?
- inApp template: Hello {{supplierName}}, You lost Auction: {{Auction_REF}}, {{AUCTION LINK}}

- pr_supervisor:
- Email status: It sends email notification to buyer team supervisor assigned to PR
- inApp Status: So Should I send inApp notification to buyer team supervisor assigned to PR?
- inApp template: Hello {{supervisorName}}, PR just Created Can you assign member to it, {{PR LINK}}

- pr_member:
- Email status: It sends email notification to assigned team member to PR
- inApp Status: So Should I send inApp notification to assigned team member to PR?
- inApp template: Hello {{supervisorName}}, You have been assigned to PR , {{PR LINK}}

- reject_rfq:
- Email status: It sends email notification to RFQ owner for rejected supplier
- inApp Status: So Should I send inApp notification to assigned team member to PR?
- inApp template: Hello {{rfqOwner}}, {{supplierName}} had been rejected the RFQ {{RFQ_REF}}, {{RFQ LINK}}

## Maybe has inApp Templates:
- project_private_invitation
- Current Status: It sends email notification to invited supplier (during create/update RFQ and from admin updates too
- inApp Status: Should I send inApp notification to invited existing teradix supplier (Invited supplier by customer only)?
- inApp template: Hello {{supplierName}}, You have been invited to RFQ {{RFQ_REF}}, {{RFQ_LINK}},

- auction_private_invitation
- Current Status: It sends email notification to invited supplier (during create/update AUCTION and from admin updates too
- inApp Status: Should I send inApp notification to invited existing teradix supplier (Invited supplier by customer only)?
- inApp template: Hello {{supplierName}}, You have been invited to AUCTION {{AUCTION_REF}}, {{AUCTION_LINK}},

- update_plan:
- Current Status: It sends email notification to all supplier users when admin change supplier plan
- inApp Status: Should I send inApp notification to all supplier users?
- inApp template: Hello {{supplierName}}, Your Company place changes from {{oldPlan}} to {{newPlan}},

## Email Notifications only:
- forget_password (he can't access platform)
- registration_complete_p (It's not verified user yet)
- verification (It's not verified user yet)

- user_company_invitation (It's not user yet)
- supplier_management_invitation (It's not user yet)

- review_submit_operation (It had been sent to operation team only)
- project_created_operation (It had been sent to operation team only)
- update_partner, (It had been sent to operation team only)
- update_partner_cr (It had been sent to operation team only)
- registration_complete_operation (It had been sent to operation team only)
- project_update_operation, (It had been sent to operation team only)
- project_sendgrid_invitation, (It had been sent to operation team only)
- auction_created_operation (It had been sent to operation team only)
- user_request_quotation (It had been sent to operation team only)
- offer_added_public (It's an offer for public RFQ (The buyer user not exists in teradix)
- public_rfq_submission (It's public RFQ submission for buyer (The buyer user not exists in teradix))
- request_access_public (It's request access to public RFQ submission for buyer (The buyer user not exists in teradix))

## Invalid notifications:
- pr_created (It's divide into two templates (pr_supervisor, pr_member)) so it's not used anymore

## No need for inApp:
- welcome_customer (I think no need for inApp notification for it)
- welcome_partner (I think no need for inApp notification for it)