Looker has the ability to filter queries based on user specific values. For example, a user associated with the “Acme” company might have their order queries restricted to Acme orders. As of Looker 4.10, you should use the
access_filter parameter to do this instead of the
In 4.16 we added a legacy feature in preparation for phasing out the old parameter (for more details see the Legacy Features docs page). The legacy feature is called Allow the access_filter_fields parameter. By default, this feature is on, which means that you can still use the old parameter. If you want to limit developers to the new parameter, turn off this legacy feature.
The new parameter is a little bit easier to understand. It also takes advantage of Looker’s User Attributes system, which makes access filters more integrated with the rest of Looker.
You can read about the old
access_filter_fields parameter, and how to use it, on our
access_filter_fields docs page.
You can read about the new
access_filters parameter, and how to use it, on our
access_filter docs page.