Does adding always_filter to an existing explore definition affect previously saved Looks and dashboard tiles?

Adding an always_filter to an existing explore definition indeed affects previously saved Looks and dashboard tiles. When an always_filter is specified, it enforces a condition on the data that will always be applied whenever that explore is accessed, regardless of any filters that the user may have set in their saved reports or dashboards.

This behavior is significant because it changes the context in which the existing Looks and dashboard tiles were originally created. Users will see the results of those Looks and tiles filtered by the new conditions imposed by the always_filter, which might lead to changes in expected results. This ensures consistency in reporting, as all users will see the same filtered dataset when accessing that explore.

Choosing to apply an always_filter can enhance data integrity and compliance with business rules but requires users to be aware of these changes in how they access and interpret their data.