...
add HF user specific authorities
rename CA table to HFUser create an HF user table (or merged to Policyholder table into an External user table ? )make PHuser more generic)
link to HF
link to user
Update the claim to take a user iso CA
CA table should become a view for compatibility
id = User ID
uuid = user UUID
code = user login
lastname = User Name
other_name = User other name
dob = user DOB (to be added if not existing)
email_id = user email
phone = user phone
HF = HF user HF
Add village specific authorities for Enrollment
drop the EO table and change the EO village to UserVillage (or merged to Policyholder table into an External user table ? )
create a EO view for compatibility
Question : Should we create a contact table to have CA without user ? (could be reused fro practitioner)
Action upon deletion of an user
...
if the users are only related to that given external partner (have no relation to other external partner ) then the user must be deactivated
Full admin
Every system need super admin to solve issues experienced by other user
change required:
add a “is_admin“ to interactive user
if “is_admin“ is true all “check permission“ must return True
block Technical user
Allow user to is_admin = True to connect to django admin