This content has been marked as final. Show 2 replies
I see several things, first and most important is that Section Access actually works prompting user and password (or whatever) and reduces data.
Starting with that:
- Fields may or may not be connected to the section access. The latter means all their data will be reduced. Said in other words, if you don't want to miss all data from a table, you need to have it linked to the section access table or any other table linked to it.
- The "*" in Section Access does not mean "all values for that field" but rather "all fields for that field and listed in this section access table". That means that if you have 100 values and you want a user to see all of them you need to get section access have 100 rows, one for each value, or do some kind of grouping (this will depend largely on your data model, though).
- In the Settings menu, Document Properties, Opening, there is a check named "Strict Exclusion" that means that, when a user does not have records linked to his entries in the section access table, then access is denied, even if the user has ADMIN as value in the field ACCESS (by the way, when connecting via client all users are USER access, even if hardcoded otherwise in the script).
- You can play with that option, uncheck it, and let the "superusers" see everything even when they don't have any data (think of general managers that have no customers associated to them, as opposed to salesperson that do). When a restricted user logs in, though, data will be reduced even when strict exclusion is unchecked.
Hope all the above makes sense and helps.