Typically, whensql_always_whereoraccess_filteris used, filter suggestions are restricted for that Explore. This prevents users from seeing a filter suggestion that does not apply to them.
For example, you might be usingaccess_filterto limit users to their company's data. If one of those users added aProject Namefilter, you might not want them to see the names of projects from other companies.
If you are certain that there are no possible values in a particulardimensionorfilterfield that would reveal sensitive information, you can re-enable filter suggestions like this:
If therearevalues in a field that would reveal sensitive information, thefull_suggestionsparameter can enable you to get properly filtered suggestions.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-22 UTC."],[],[],null,["# bypass_suggest_restrictions\n\n\u003cbr /\u003e\n\n\u003e Use caution when using this parameter, as it can reveal sensitive data if used incorrectly.\n\nUsage\n-----\n\n```\nview: view_name {\n dimension: field_name {\n bypass_suggest_restrictions: yes\n }\n}\n```\n\nDefinition\n----------\n\nTypically, when [`sql_always_where`](/looker/docs/reference/param-explore-sql-always-where) or [`access_filter`](/looker/docs/reference/param-explore-access-filter) is used, filter suggestions are restricted for that Explore. This prevents users from seeing a filter suggestion that does not apply to them.\n\nFor example, you might be using [`access_filter`](/looker/docs/reference/param-explore-access-filter) to limit users to their company's data. If one of those users added a **Project Name** filter, you might not want them to see the names of projects from other companies.\n\nIf you are certain that there are no possible values in a particular [`dimension`](/looker/docs/reference/param-field-dimension) or [`filter`](/looker/docs/reference/param-field-filter) field that would reveal sensitive information, you can re-enable filter suggestions like this: \n\n dimension: project_name {\n sql: ${TABLE}.project ;;\n bypass_suggest_restrictions: yes\n }\n\n-\n\nIf there *are* values in a field that would reveal sensitive information, the [`full_suggestions`](/looker/docs/reference/param-field-full-suggestions) parameter can enable you to get properly filtered suggestions."]]
