Skip to main content

Locking Quick Filters Bar Filters: Filter-Level Permissions on Dashboards

Locking Quick Filters Bar Filters: Filter-Level Permissions on Dashboards

The quick filters bar already lets you decide who may change a dashboard's filters. Locks let you decide which filters they may change. A bar editor can lock any single filter button, or the date range, to its saved value; everyone else keeps changing the other filters exactly as before. That turns the bar's permission ladder into filter-level permissions: a per-site dashboard whose site is fixed but whose channel and priority are free, or a live wallboard whose date range nobody can drift off.

This guide covers locking and unlocking, what a locked filter looks like at each permission level, and how locks interact with saved defaults and per-tab bars. Setting a bar up in the first place is covered in Quick Filters Bar on Dashboards: Setup, Permissions, and Daily Use, and renaming, colouring and reordering the buttons in Customizing the Quick Filters Bar: Filter Buttons and Per-Tab Bars.


Before you start

  • You need a dashboard that already has a filters bar with the filters you want on it.

  • Locking and unlocking needs the bar's Edit tier, shown on the dashboard's access page as Can configure, lock/unlock, and rename filter bar. Anyone who can edit the dashboard has it automatically.

  • Locks matter most for the Change and Save tiers. Those are the people who could otherwise change any value on the bar. Read-only viewers were never able to change anything, so a lock changes nothing for them.


1. The permission ladder, and where locks sit on it

Bar permissions are granted per dashboard, per user or user group, on Manage Users Access To Dashboard. The Quick Filters Bar Permissions block has four levels, and each one includes the ones before it:

  • See: the bar is visible and shows which filters are applied; nothing can be changed.

  • Change: can pick values in the buttons and apply them for their own session. The right level for most people.

  • Save: can also press Save as Default and change what everyone starts from.

  • Edit: can also add, remove and rename buttons, turn the date range on or off, and lock or unlock filters.

A lock is the Edit tier reaching down into the Change and Save tiers: it says "this one value is not yours to change, whatever your level lets you do with the rest". Only an Edit-tier user can put a lock on or take it off, and while a filter is locked nobody, editors included, can change its value.


2. Lock a filter or the date range

Put the dashboard into edit mode with the Edit button, or open the gear menu at the right end of the bar and tick Edit filter buttons if you can shape the bar but not the dashboard. Every filter button grows its editing controls, and among them is a padlock toggle. The date range has its own padlock, just to the right of the date button.

Click the padlock to lock that filter at its saved value. The tooltip on the toggle says what is about to happen: Lock this filter's value. Only filters bar editors can unlock it. Click again to unlock. The toggle reads as pressed while the filter is locked.

  • A lock holds the saved value, so save first. If you have picked a new value on the button and not yet saved it, locking is refused with Save or revert the change to Channel before locking it. Press Save as Default (or Revert to Default), then lock.

  • Locks are saved as you click. There is no separate save step for the lock itself, and it applies to everyone the moment it is on.

  • Locks survive Revert to Default, which puts saved values back but never clears a lock.

  • Filter buttons and the date range lock independently. Lock the date on a live board and leave every other button open, or lock the brand and leave the date free.


3. What a locked filter looks like to everyone else

For a user at the Change or Save tier, a locked button shows a small lock icon where its chevron would be, and it does not open. The buttons around it open and apply as normal. Hovering the count on a locked button still lists the values it is filtered to, so people can always tell what a dashboard is scoped to even when they cannot change it.

Two audiences see no difference at all:

  • Read-only viewers (See tier). Every button was already locked for them, so a locked and an unlocked button render identically. Nothing gives the lock away.

  • Editors outside edit mode. They see the lock icon like everyone else. The padlock toggles appear only in edit mode, which keeps the everyday bar uncluttered.

The Enabled toggle at the right of the bar, which switches the whole bar off for your session, is now shown only to bar editors. For everyone else the bar's filters always apply, so a lock cannot be sidestepped by disabling the bar.


4. Changing a locked value

The editor flow is unlock → change → Save as Default → relock. Unlock the filter in edit mode, pick the new value, save it as the default so everyone starts from it, then lock it again. The date range unlocks in place, so an editor can change it without reloading the page.

The lock is enforced when a save is made, not just drawn on the screen. Every route that writes a bar's saved values, including the in-app Save as Default, Save for this tab only and the User Access API, checks the locked filters first, and a save that would change a locked value is refused as a whole. Resending the current value is fine, so saving the other filters on the bar always works.

If someone locked a filter while you had the page open, your next save of that filter is refused with a message naming it: Channel was locked by a filters bar editor, so that change was not saved. The button flips to its locked look, that one change is reverted, and any other unsaved changes you made are kept.


5. Locks and per-tab bars

On a dashboard with tabs, a single tab can have its own filters bar. A tab bar created from the default bar copies its locks, so a locked site stays locked on every tab. Save for this tab only is checked against the locks too: a tab save that would change a locked value is refused, and no tab bar is created. Tab-level access is covered in Customizing the Quick Filters Bar.

One surface cannot lock the date: a World Heat Map's bar has no date button, so there is nothing to lock there. Its filter buttons lock the same way as a dashboard's.


6. Patterns that use locks well

  • Per-site or per-vendor dashboards. One dashboard per site, the site (or hub, or brand) button locked, channel and priority free. Team leads slice their own data without ever seeing another site's, and you maintain one layout.

  • Live wallboards. Lock the date range to today so a stray click cannot turn a live board into last month's numbers, and leave the queue button open for whoever is watching.

  • A shared scorecard with one non-negotiable. Lock the ticket form or request type that defines the report, and let the rest of the bar stay flexible.

  • Combine with button styling. Give the locked button a colour so it reads as the fixed scope of the page rather than a control that happens not to open.

Everything else about the bar stays configurable alongside locks: up to six filter buttons plus the date, saved filter sets as a single button, renamed and coloured buttons, drag-to-reorder, per-tab bars, and the four-level permission ladder per user or group.


Troubleshooting

  • I do not see a padlock on the buttons. You are not in edit mode, or you do not hold the bar's Edit tier on this dashboard. Ask whoever manages the dashboard's user access for Can configure, lock/unlock, and rename filter bar.

  • Locking is refused. The button has an unsaved change. Save as Default or Revert to Default first, then lock.

  • My save was refused and one button turned locked. An editor locked that filter after you loaded the page. Your other changes were kept; reload to see the current locks.

  • A locked button still shows a filter I did not choose. That is its saved default. Only an Edit-tier user can unlock it and change the default.

  • A widget's own filter seems to override the bar. The bar layers on top of each widget's saved filters; where both set the same filter, the bar's saved value wins for the page. Widget-level filtering is explained in Comprehensive Guide to Filters in Qvasa Dashboards.


Did this answer your question?