View the original community article here
Last tested: Sep 8, 2020
Yes. We don't need to setup the access filter again, once the access filter from the original explore is also considered on the extended one.
Considering the explore Users below, which contains an access filter on the field users.state:
explore: users {
view_name: users
access_filter: {
field: users.state
user_attribute: state_ext
}
We have are extending this explore as a User Ext explore and not defining the access filter:
explore: users_ext {
extends: [users]
}
The state_ext user attribute contains the Alabama value for a specific user, and both explores User and User Ext contains the user-specific data restriction applied.
This content is subject to limited support.