Skip to main content

World Heat Maps: Shared Default Filters, Quick Filters Bar, and Access Control

World Heat Maps: Shared Default Filters, Quick Filters Bar, and Access Control

The World Heat Map shows your live support floor on a map: active messaging sessions and ongoing phone calls, colored by country and city, refreshing as new interactions arrive. This guide covers how to set the map up once for your whole team: save default filters that every viewer starts from, add a quick filters bar with the handful of filters most people need, run more than one map, and control who can view or change each map.

Before you start

Feature flags. The World Heat Map must be enabled on your account. The quick filters bar is a separate account feature, the same one dashboards use. If you do not see the quick filters bar controls described below, ask Qvasa Support to enable it.

Live data. The map plots messaging sessions and phone calls that carry a location, so it is only as busy as your live traffic. Every viewer sees the same underlying data; permissions decide who can change the setup.

Who can do what. Viewing the map and curating it are separate permissions. Set them up first (next section) so the right people can save defaults and manage access.

1. Grant account-level permissions

Account admins set World Heat Map permissions per user under Settings > Account Members, on the member's edit page. The permissions form a chain, from view-only up to full control:

  • Can view world heat map: see the account's default map. People with only this permission see the map exactly as it was configured and cannot change the setup.

  • Can be added to world heat maps: can be granted access to maps other than the default (see the Access section below).

  • Can be made an editor of world heat maps: can be given edit rights on a specific map.

  • Can create world heat maps: can create new maps from the World Heat Maps list.

  • Can edit all world heat maps, Can change default world heat map, Can destroy all world heat maps: account-wide curator rights. Changing the default additionally requires the admin role.

Users who were already admins before this feature shipped do not receive the new permissions automatically. Grant them to whoever should curate maps.

2. Know your way around the map

Open the globe icon in the sidebar to reach the account's default map. The bar across the top holds everything about the map as an object:

  • Title and pencil: rename the map in place.

  • Default badge: the gold star marks the account default, the map the globe icon always opens. On other maps, admins with permission see a Make default button here instead.

  • Quick filters bar: the chips viewers use to narrow the map without opening the full filters panel (section 4).

  • Access: manage who can see and edit this map (section 6).

  • All Maps: open the list of every map you can see, in a new tab.

Below the bar, the Countries, Cities, Phone Calls and Messaging Sessions toggles change what is drawn, and Filters opens the full filter panel.

3. Save default filters for every viewer

Filters are saved on the map itself, not on your user. Whatever you save as the default is what every viewer starts from when they open that map.

  1. Click Filters, pick the filters you want (for example a country, a ticket tag, or a queue) and click Apply & Save. The map redraws with the filters applied.

  2. A dot appears next to the save control in the filter row to show the applied filters differ from the map's saved default. Click the save as default button to store them as this map's default for all viewers.

  3. Use Clear to remove all applied filters. Clearing does not change the saved default until you save again.

Saving defaults requires edit rights on the map (a map editor or an account-wide curator). Viewers can still apply their own filters during a session, but the next time they open the map they start from the saved default again.

4. Add a quick filters bar

The quick filters bar puts a small set of chips at the top of the map so most people never need the full filters panel. It works the same way as on dashboards: Comprehensive Guide to Filters in Qvasa Dashboards.

  1. On a map you can edit, click the add a quick filters bar button in the top bar. The bar appears with an Enabled toggle.

  2. Click + to add a chip and choose the filter, for example Sunshine Conversation Country or Ticket Country. Remove a chip with its x.

  3. Viewers pick values in the chips to narrow the map. Their chip choices sit on top of the map's default filters and never change them.

Two things are different from dashboards: a map bar never has a date chip (the map always shows what is live right now), and agent-population chips and filter sets are not offered, because the map is about interactions, not agents.

5. Run more than one map

Each map has its own name, default filters, quick filters bar and access list, so you can keep a global floor view as the default and give a team its own curated map, for example a front-office map filtered to care and disruption tickets.

  • Open World Heat Maps in the sidebar (or All Maps from any map) to see every map you have access to, who created it, and your access level.

  • Click Create New Map to add one. New maps start with no default filters and no quick filters bar.

  • The star column marks the account default. Admins with the change-default permission can promote another map from its title bar.

  • Delete a map from its row. The default map cannot be deleted while other maps exist; make a different map the default first.

People who only have the view permission never see this list; the globe icon takes them straight to the default map.

6. Control access per map

Click Access in a map's top bar to open its access page. It works like dashboard access management: Managing User Permissions in Qvasa.

  • Add Qvasa User To World Heat Map adds an individual with view-only rights. Edit the row to grant Inspect (drill into the sessions and calls behind a marker), Edit (change filters and the bar), User Access (manage this page) and Delete, plus the quick filters bar rights to see, change, save defaults for, and edit the bar. A user can only be given rights their account-level permissions allow.

  • Add Qvasa User Group To World Heat Map grants a whole group at once. A group must first be marked as eligible for world heat maps on its group page under Settings. Group rights can exceed a member's own account-level permissions, and the page shows each member's highest permission from the group.

  • The map's creator is locked in with full rights, and users with the account-level edit all world heat maps permission are listed below the tables so it is clear who can change the map without a per-map grant.

The default map is special: everyone with the view permission can see it without being added here. Non-default maps are only visible to the users and groups on their access page and to account-wide curators.

What done looks like

  • The globe icon opens your curated default map with the right filters already applied for every viewer.

  • The quick filters bar shows the three or four chips your team actually uses, and changing a chip never disturbs the saved defaults.

  • Viewers see the map but cannot change the setup; the people you named as editors or curators can.

Troubleshooting

  • Someone cannot see the World Heat Maps list. They only have the view permission. Grant Can be added to world heat maps or higher, or add them to a specific map from its access page.

  • There is no quick filters bar button. Either the quick filters bar feature is not enabled on the account, or the user lacks edit rights on that map.

  • Make default is missing. Changing the default requires the admin role plus the Can change default world heat map permission.

  • A group cannot be added. Mark the group as eligible for world heat maps on its group page first.

  • Filters used to revert a few seconds after applying. This was a bug in how the map handled overlapping data requests and is fixed. If you still see it, reload the page and contact support with the map name.

Did this answer your question?