SQL Server 2016 temporal tables design best practice

Question

with SQL Server 2016 temporal table feature available what is best practice to model for soft deleting a row feature. eg below are 2 different cases.

1. customer, order, orderline tables are there and if I delete customer should i do soft delete by adding isDeleted column? Or do hard delete with backing of temporal tables? if i use temporal then what if i need to undelete that customer and his orders, orderlines.

2. role, permission, rolepermission table is there. Now if someone changes role permissions should I clear all permission for the role in rolepermission table and add fresh entries? Or should we implement isdelete column in rolepermission table and do upsert instead of hard delete.

am not good at db design and wanted some expert to point me in right direction.

Answer 1

for now we are doing soft delete in all tables and using this library to ensure we dont have to write lot of isdelete filter in ef code.

https://github.com/zzzprojects/EntityFramework-Plus