Hi Kris, You are 100% right.
I do not think there are any pros and cons in particular. In my opinion it all depends on report requirement. With section access implemented in QV you are "sort of" limited when distributing reports to individual users. Showing for example sales contribution to total sales in region requires then separate dataset for sales on region level.
I personally think implementing filter is a more clear and reliable solution. This also help avoid all anomalies where data reduction based on section access can play main role. As you know section access removes records from data set where filter only filters such record - hence you are still able access it by using an expression with set analysis for example.
On pros side - Section access filter based on recipient takes off one layer of work (which is looking after a filter in NPrinting), but i still prefer using apps without section access
bit chaotic thoughts i guess - so to sum up I prefer using filters!
So after thinking about this more, if one uses NP web console filters to mimic section access, if I had a scenario like the one below, I would have to create a separate filter per person/user in NP web console, and assign the respective filter to each user, correct? There is no way to some how dynamically do this and just have a single filter that can get applied to all users (all users that are not kris, that is), correct? Thanks again.
Yes, it is correct.
Instead of creating users and filters manually you can import them from an Excel file as you can see in the help site page http://help.qlik.com/en-US/nprinting/June2017/Content/Recipients&Users/ImportUsersFiltersGroups/Import-Users-Filters.htm
Sometimes it could be faster to create the Excel file instead of manually create each user, each filter and match them.