Hi Team,
I have a question here based on section access.
| Payee Name |
|
ID |
| SBI |
|
1 |
| BHIM UPI |
|
2 |
| Google Pay |
|
3 |
| PhonePe |
|
4 |
| Amazon UPI |
|
5 |
SSO is based on ID of the user logs in. If Direct user logs in, he should be able to see all the indirect user's data. If the indirect user logs in he should see his own data.
In the above scenario SBI is the parent under which UPI apps made the transaction.
It will be related in the below table :
| Payee Name |
Payee Type |
ID |
Flex ID |
| SBI |
Direct |
1 |
11 |
| BHIM UPI |
Indirect |
2 |
11 |
| Google Pay |
Indirect |
3 |
11 |
| PhonePe |
Indirect |
4 |
11 |
| Amazon UPI |
Indirect |
5 |
11 |
Flex ID is the key column for linking Direct and indirect Payee.
Issue : If the section access is applied on the ID, SBI will not be able to use the other user's data.
If i use the 2nd table after section access and join the ID with Flex id, users will be able to see other user's data.
Can anyone suggest how to apply section access or restrict the data based on the above scenario.
