What the User Group Login Report tells you about agent access

VICIdial's User group system controls which campaigns an Agent can work, which reports they can see, and what actions they are allowed to take. The User Group Login Report gives you a single view of who has actually logged in — organized by user group — along with the details of their most recent session. It is the go-to screen for access reviews and for tracking down agents who have not logged in for a long time.

What the report covers

For every agent who has ever logged in, the report shows their name, user ID, and user group. Beyond that identity block, it displays two date columns — first login date and last login date — which give you the full active window for that account. The rest of the columns describe the most recent login specifically:

• Campaign — the campaign the agent was assigned to when they last logged in.
• Server IP address — the VICIdial server they connected to.
• Computer IP address — the workstation or browser origin, which can help identify an agent logging in from an unexpected location.
• Extension — the Extension the agent registered when they last started their session.
• Browser and version — the agent's client browser, useful for diagnosing repeated issues tied to a specific environment.
• Phone login, Server Phone, and Phone IP address — the SIP phone credentials and network origin for the audio leg of the last session.

Reading the data by user group

The report groups results by user group, which means you can quickly scan an entire team of agents in one block. If you have user groups that map to specific campaigns — for instance a group for your outbound sales floor versus a group for your inbound support queue — you can visually confirm that no agent is appearing under the wrong group, or that an agent has not been logging into a campaign they are not supposed to be assigned to.

The last login date is particularly useful for identifying stale accounts. An agent whose last login was several months ago may have left your organization, and their account should be disabled to prevent unauthorized access. Sorting by last login date and working through the oldest entries is a simple routine to add to your monthly access review.

What the phone columns tell you

The Phone IP address column shows where the Softphone or hardware phone was registering from. If your policy requires agents to work from a specific office network, an unexpected phone IP — especially a residential or VPN range — indicates a policy breach or a misconfigured remote setup. Combined with the Computer IP address, you can usually distinguish a fully remote session from an agent who moved their softphone but kept their browser on the office network.

How login data flows into the report

flowchart TD
  A["Agent logs in"] --> B["VICIdial records login event"]
  B --> C["Store: user ID, user group, campaign"]
  B --> D["Store: server IP, computer IP, phone IP"]
  B --> E["Store: extension, browser, phone login"]
  C --> F["User Group Login Report"]
  D --> F
  E --> F
  F --> G{"First login ever?"}
  G -->|Yes| H["Set first_login_date"]
  G -->|No| I["Update last_login_date + most recent session columns"]

Using this report alongside monitoring logs

The User Group Login Report shows access — who logged in from where. If you also need to know which of those agents were monitored by a manager during a given period, pair this report with the Real-Time Monitoring Log, which records every listen-in session. Together the two reports give you a full access-and-oversight picture for any agent account.

For the wider framework of what VICIdial tracks at the server level, start with the server health and capacity guide. For a look at Latency across currently logged-in agents, the server performance report breakdown is the next logical read.

Running these reviews on a managed box means the reporting infrastructure is already in place. See VICIfast plans to get a fully configured VICIdial environment live in under 40 seconds.