Controlling Which Agents See a Custom Report in VICIdial

VICIdial ships with a long list of built-in reports, but most call centers eventually want their own links sitting right next to them. The Custom Reports Admin page is where you add, modify, and delete those links. Anything you add here shows up on the main Reports page, and you control who is allowed to see it.

This is handy for more than just outside reports. You can point a custom link at one of VICIdial's own pages and pre-fill it with variables, so a frequently used view of a Real-time report or a Whiteboard report becomes a one-click shortcut instead of a form you fill out every morning.

What each field does

Four fields do most of the work when you add a link.

• Report Name is how the system refers to the report for access control and secondary-server use. It must be unique. You cannot reuse a name from another custom report, and you cannot reuse the name of a standard built-in report.
• Domain is where the report lives. Leave it blank when the report sits on the same server as your web admin, and VICIdial treats the link as local.
• Path name is the path on that domain. The domain and the path name are joined together to form the complete URL the link points at.
• Preset constants let you attach fixed variable values to the link. Pre-defined date values like today, yesterday, or 7days save you from re-typing parameters on a report that takes several inputs.

Preset constants are the shortcut trick. If you always look at the same agent numbers for the previous day, you can build a link that opens an Agent performance view already scoped to yesterday. The variable values are URL-encoded before they are stored, so you do not have to worry about escaping them yourself.

How User Group controls visibility

The field that catches most people out is User Group. When you add or edit a custom report link, you pick one or more user groups that are allowed to access it. An agent or user only sees the link on the Reports page if they belong to one of the selected groups. If their User group is not on the list, the link simply does not appear for them.

This is the same membership model VICIdial uses across the rest of its access rules, so it lines up with how you already organize people. A floor lead in the Sales group sees the Sales dashboards, a quality reviewer in the QA group sees the audit links, and neither sees the other side's reports cluttering their page. Because access is decided by group membership rather than by individual login, you manage it once and it follows people as they move teams.

The flow below shows how that decision plays out each time someone opens the Reports page.

flowchart TD
  A[User opens Reports page] --> B[VICIdial reads the users user group]
  B --> C{User group is on the report link list}
  C -- yes --> D[Show the custom report link]
  C -- no --> E[Hide the link from this user]
  D --> F[User clicks and report opens]

A few habits that keep it clean

Name reports for what they show, not who built them, so the unique-name rule never becomes a guessing game. Decide group access when you create the link rather than after, because a report that quietly exposes a sensitive KPI to the wrong floor is harder to walk back than to prevent. And when a report moves servers, update the Domain field instead of deleting and re-adding the whole entry, so the group access you set up survives the move.

Custom report links are one slice of VICIdial's admin utilities. For the full tour of the bulk and admin tools that sit alongside them, read our guide to VICIdial admin bulk tools. If you want a refresher on the page these links live under, see what the Custom Reports Admin page does.

Setting all of this up yourself means standing up a working VICIdial box first. If you would rather skip the server work and get a configured dialer in under 40 seconds, see VICIfast pricing.