You're not very clear about what exactly these IDs refer to?
In general, you could store authorizations in an external DB and use conditional show to show/hide objects, use the OMIT clause in Section Access to hide entire fields, and use data reduction to restrict access to table rows. YMMV.
Good input. However, that does not do the trick. I used your solution in several other solutions when only specific values should be visible to particular users. Sometimes OMIT works and sometimes I have just added a field for a specific business unit to allow the BU-managers to access only their data. The challenge here is the opposite. I do not want to have to specify all users that should have access to everything. Maybe there is a really simple solution, but it still escapes my creativity. Any thoughts? The ID connect rows to financial information.
I get your point. Unfortunately there is no easy quick-and-dirty solution for this type of challenge, as QV - through its associative logic - needs an explicit specification of every value that shouldn't be reduced away.
If I understand it correctly, you are looking for an authorization specification technique like this:
Adam, * - 1009
Bernd, * - 8
*, * - 8 - 439 - 1009
the last line meaning all others should have access to everything except the reserved IDs. You can build a solution like this using standard QlikView script techniques but it may become complex code, depending on your requirements.