How Allowed Queue Groups scopes report visibility for a group

Allowed Queue Groups is a setting on a VICIdial user group that decides which queue groups the members of that group can see inside the reports that work with queue groups. A user group is the object that lets one setting cover a whole team. The default is All Queue Groups, so until you change it, everyone in the group sees every queue's data.

Queue groups, briefly

A queue group is a label that ties together a set of inbound queues so they can be reported on as a unit. When several inbound campaigns share a Call queue, grouping them lets a report total the whole set at once. Each Ingroup you build for inbound traffic can be rolled into one of these groups, and queue-based reports then summarize per group rather than per individual queue.

Allowed Queue Groups is the filter that says which of those groups a given team's managers are allowed to look at.

What it actually scopes

This setting scopes the data, not the screen. A manager in the group can still open a queue-based report, but the queue groups they did not get assigned simply will not appear in the results. A lead over the sales queues sees sales numbers; the support queues stay invisible to them, even in a shared Real-time report.

flowchart TD
  A[Open queue based report] --> B{Allowed Queue Groups}
  B -->|All Queue Groups| C[Show all queues]
  B -->|Selected list| D[Filter to chosen groups]
  D --> E[Render report rows]
  C --> E

Because the rule lives on the group, it covers every qualifying user in it without per-person setup. Add a new team lead to the User group and they inherit the same queue scope automatically.

How it pairs with Allowed Reports

Allowed Reports and Allowed Queue Groups work on two different axes. Allowed Reports decides which report a manager can open. Allowed Queue Groups decides which rows that report returns. Use them together to give a regional supervisor only the queue reports they need, showing only their own region's queues. Skip one and you get a leaky setup: open the report but show every region's data, or scope the data but leave reports the supervisor should not even reach.

A worked example makes it concrete. Say you run inbound support out of three regions, each with its own set of queues bundled into a regional queue group. You give each region's leads a User group whose Allowed Queue Groups is set to just that region. Now when any of those leads opens a queue summary, they see only their own region's call volumes and wait times. The same report, run by a national manager whose group is set to All Queue Groups, totals all three regions at once. One report, two very different views, decided entirely by the group setting.

This is also the cleaner alternative to handing out separate logins per region or maintaining duplicate report pages. You keep one set of reports and let the group scope do the filtering, which means less to maintain and far less chance of a stale page leaking the wrong queue's numbers.

Note: this only affects reports that are actually built around queue groups. Reports that summarize by Campaign or by agent are unaffected, so do not expect this single setting to hide all of a team's data everywhere. It is one scoping tool among several on the group.

To see how queue scoping fits the broader group model, read our users and groups multi-team guide. The field itself is documented in how to modify a VICIdial user group.

Want per-team report scoping without running the server yourself? Start a VICIfast trial and have a managed VICIdial live in under 40 seconds.