How Allowed Campaigns on a user group scopes agent logins

Allowed Campaigns is one of the most important settings on a VICIdial user group. A user group is the admin entity that bundles agents, and this setting decides exactly which campaigns those agents are offered when they log in. Get it right and a team only ever sees the work meant for them; get it wrong and an agent can accidentally dial the wrong client's leads.

What the setting actually is

On the Modify User Group screen, Allowed Campaigns is a selectable list of every Campaign on the system. Whatever you select is the menu of choices presented to members of the group at the agent login screen. There is also an ALL-CAMPAIGNS option, which lets the group see and log into any campaign that exists, present or future.

This is a server-side gate, not a UI suggestion. An Agent cannot type in a campaign ID they are not entitled to; the list they are shown is the list they are allowed to use. That makes it a clean separation tool when you host more than one team or client on a single box.

How a login resolves

sequenceDiagram
  Agent->>VICIdial: Submit login
  VICIdial->>DB: Read user group
  DB-->>VICIdial: Allowed Campaigns list
  alt ALL-CAMPAIGNS
    VICIdial-->>Agent: Show every campaign
  else specific list
    VICIdial-->>Agent: Show only allowed campaigns
  end
  Agent->>VICIdial: Pick campaign and proceed

ALL-CAMPAIGNS versus a scoped list

ALL-CAMPAIGNS is convenient for a single-team shop where everyone works everything. It is risky the moment you run separate clients, because a future campaign you add for one client is automatically visible to every group set to ALL-CAMPAIGNS. The safer pattern for multi-team setups is an explicit list per group, even if it means editing the group each time you launch a new campaign.

Keep these points in mind:

• A new campaign is NOT visible to a scoped group until you add it. This is a feature, not a bug.
• Removing a campaign from the list does not log out agents already running it; it just hides it at the next login.
• If an agent reports a campaign is missing, the group's Allowed Campaigns list is the first place to look.

A worked example

Say you host two clients on one box: Acme and Globex. You create a group acme_agents with Allowed Campaigns set to only the Acme campaigns, and globex_agents scoped to the Globex campaigns. Now an Acme agent who logs in only ever sees Acme work, and there is no way for them to land on a Globex lead by mistake. When Acme launches a third campaign next month, you add it to acme_agents and nobody else is affected. That single edit is the whole separation story.

Contrast that with both groups set to ALL-CAMPAIGNS: the moment the Globex campaign goes live, every Acme agent can see and dial it too. On a shared box that is a real compliance and data-handling problem, not just an annoyance.

How it pairs with other scoping

Allowed Campaigns controls where an agent can log in. A separate setting, Agent Status Viewable Groups, controls who they can see and transfer to once inside. Together they define a team's blast radius. For Skills-based routing across multiple Ingroup queues, you will usually pair a scoped campaign list with carefully chosen viewable groups so transfers stay inside the right team.

For the companion setting, read what Agent Status Viewable Groups controls. It also helps to understand how login rights interact with VICIdial user levels, and for the full structure see the users and groups guide.

Running several clients on one dialer and want the separation handled cleanly from the start? Our managed servers ship ready in under 40 seconds; see the pricing page.