Split User Role / Invitation

[minotogna]

Where necessary, add relevant comments in the user invitation flow

• Split db, types and datamigration
• Country collaborators page: split collaborators and invitations tables (2 tables, add plus button on top of invitations table)
• Update country status change confirm pop up
• Remove deprecated component: componentsUserList
• Verify user invitation process (check API/Controller/Repository)
• Verify admin invitation page
• View
• Verify admin collaborators page (invitation are also included in the users list)
• Verify introduction contact user list
• Country summary materialized : Invitations count
• Country Home Page update to single list
• Verify edit user (and user role props) works
  • Test editing collaborator with admin
  • Test inviting new collaborator, accepting invitation and update information after redirect, after Edit profile
• Update UI as in given layout (Slack)
• Admin add or remove multiple roles
• Add user download buttons (country home / collaborators) (separate PR)

---

• Setup E2E testing

  • Init DB:
    • Controller OUTPUT: Metadata and data for all countries 2020 and 2025
    • Controller INPUT

• Test cases

  • Test: user login (admin)
  • Test: User invite (admin invite all roles, all combinations) (Verify working from admin page invitations)
  • Test: User accept invitation with login

---

[sorja]

Let's update:

• Country collaborators:
  • Single list with mixed users and invitations (pending users)
• Admin manage collaborators

New view:

country_user_summary

columns:

name
surname
fullname?:
country_iso
role: the role for the given country_iso | nullable
invitation: the invitation for given country (admin page> text disabled -> something noting: pending invitation)

either is active

Type:

type CounrtyUserSummary = {

}

Server

CountryUserRepository.{}