<br />

> Use caution when using this parameter, as it can reveal sensitive data if used incorrectly.

## Usage

```
view: view_name {
  dimension: field_name {
    bypass_suggest_restrictions: yes
  }
}
```

|---|---|
| Hierarchy [View File](https://docs.cloud.google.com/looker/docs/2618/reference/param-view) [`view`](https://docs.cloud.google.com/looker/docs/2618/reference/param-view-view) [Field Type](https://docs.cloud.google.com/looker/docs/2618/reference/param-field) `bypass_suggest_restrictions` | Possible Field Types Dimension, Dimension Group, Filter, Parameter <br /> Accepts A Boolean (yes or no) <br /> |

## Definition

Typically, when [`sql_always_where`](https://docs.cloud.google.com/looker/docs/2618/reference/param-explore-sql-always-where) or [`access_filter`](https://docs.cloud.google.com/looker/docs/2618/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.

For example, you might be using [`access_filter`](https://docs.cloud.google.com/looker/docs/2618/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.

If you are certain that there are no possible values in a particular [`dimension`](https://docs.cloud.google.com/looker/docs/2618/reference/param-field-dimension) or [`filter`](https://docs.cloud.google.com/looker/docs/2618/reference/param-field-filter) field that would reveal sensitive information, you can re-enable filter suggestions like this:

    dimension: project_name {
      sql: ${TABLE}.project ;;
      bypass_suggest_restrictions: yes
    }

-

If there *are* values in a field that would reveal sensitive information, the [`full_suggestions`](https://docs.cloud.google.com/looker/docs/2618/reference/param-field-full-suggestions) parameter can enable you to get properly filtered suggestions.