Skip to main content

Using row filters

Limit which rows a person, group, or service account can query inside a table.

When to use this​

  • Use it when the user should see only one region, unit, portfolio, period, or domain.
  • Use it when the table is shared by several areas.
  • Use it to reduce exposure without creating separate copies of the data.

Before you start​

  • Define the slicing criterion with the data owner.
  • Confirm which column represents the slice you want.
  • Check that the filter does not remove data the work needs.

Step by step​

  1. Open the data rule.
  2. Select the table that will receive the restriction.
  3. Open the row filter options.
  4. Enter the slicing criterion using the interface's fields.
  5. Simulate to confirm the expected effect.
  6. Review the summary and save.

What happens next​

  • Queries return only the rows covered by the filter.
  • The rule stays auditable and can be adjusted.
  • Users may see fewer rows than other roles, even querying the same table.

Common errors​

  • Too broad a filter: it exposes more records than necessary.
  • Too narrow a filter: the result comes back empty or incomplete.
  • The wrong criterion: check with the data owner before saving.

Good practice​

  • Test filters on small groups before applying them widely.
  • Document the business criterion used for the slice.
  • Combine row filters with masks when the table holds sensitive data.

Next steps​