While the application values (those not in the section access table) may concatenate or create synthetic keys, the last table with section access to be loaded will remain and override the previous ones.
Say I'm DOMAIN\USER1 and I have a File1.qvw with section access with the following line
USER, DOMAIN\USER1, SPAIN
Then I have File2.qvw that binary loads File1.qvw and section access with
USER, DOMAIN\USER1, FRANCE
When I open File2.qvw, I will only see FRANCE, the section access table in File2 overrode the previous one.
If you want to have both values, keep the section access code in a QVS file that you load via $(Include=). You can play with the name of the file and string functions to load different files in that include.
For example, I have a section access DEVELOPMENT.qvs which allows all developers to open the app and see fake data, not real, production data and PRODUCTION.qvs with all users including developers. I could choose which table I want to load based on which server the app is hosted.
Similarly, I could load both section access tables as normal tables, so they concatenate, then load that table with all values into a section access table via RESIDENT.
.png "Former Employee"){kind=icon}
.png "Miguel_Angel_Baeyens"){kind=avatar}
