FAQ/Questions/Applying-Security.md
... ...
@@ -67,14 +67,10 @@ else
67 67
68 68
##Field Level Access
69 69
70
-Field access provides a way of limiting what a user sees in the application. This is taken care of through a simple and easy-to-work-with property in the Izenda settings framework.
71
-
72
-[[Please see this example|Controlling access to fields]]
70
+Field access provides a way of limiting what a user sees in the application. You can use the [[FieldsRegex|/API/CodeSamples/FieldFilterRegex]] property to set a general filter on what fields users can select when building reports or you can use the ``PreExecuteReportSet()`` method, demonstrated below.
73 71
74 72
**Record Level Security Integration**
75 73
76
-- Row and Cell Level Access
77
-
78 74
Izenda Reports supports the unique feature of being able to hide report data on-the-fly on a per user basis. Consider this scenario: Bill, Mary, and John are all sales people. You want to generate the same report for each of them, but with different sales territory data. With Izenda Reports, simply generate one report, give each user a link to that report, and change the filter for each user to show the specific sales data.
79 75
80 76
In this example, the ``PreExecuteReportSet`` method adds hidden filters to limit data on-the-fly.