What the VICIdial user permission checkboxes do

Every VICIdial user record carries a long list of permission checkboxes that decide exactly which admin screens that person can touch. A User group, the named bucket that ties agents and managers to allowed campaigns, controls reach, while these checkboxes control capability. The two work together: a group decides which campaigns you can see, and the permissions decide what you can do once you are looking at them. This post gives you a plain tour so you can grant a manager just enough access and nothing more.

Modify versus Delete

Most permissions come in pairs. A Modify option lets the user change settings on a kind of object, and the matching Delete option lets them remove that object entirely. Modify Users lets someone edit other accounts, while Delete Users lets them remove accounts of equal or lesser user level. The same split repeats for lists, campaigns, in-groups, scripts, and filters. Almost every one of these defaults to 0, meaning off, so a fresh account can see very little until you deliberately turn options on. That default-off behaviour is your friend: nobody accidentally inherits dangerous access just by being created.

• Modify Users and Delete Users control other accounts.
• Modify Lists and Delete Lists control Lead list records, including resetting lists.
• Modify Campaigns and Delete Campaigns control the Campaign settings that drive dialing.
• Modify In-Groups and Delete In-Groups control each inbound Ingroup.

Permissions that are not pairs

Some options stand alone. View Reports lets the user open the reports screens, but it also requires a user level of 7 or higher to work. Change Agent Campaign lets a manager alter live settings on a campaign an agent is logged into, such as switching their selected inbound groups from the real-time report. Load Leads lets the user run the web lead loaders. Modify Leads is graded rather than on-or-off, where higher numbers unlock more fields and a value of 5 is read-only. Knowing which permissions are graded saves you from accidentally handing out write access when you only meant to allow a look.

Build roles, not one-off toggles

The easiest way to keep this manageable is to think in roles. A floor supervisor might get Modify Campaigns, Modify Lists, and View Reports, but none of the Delete boxes. A reporting analyst might get only View Reports and Export Reports at level 7. A senior administrator gets the Delete options too. Decide the role first, list the boxes it needs, then apply the same set to everyone in that role. When you onboard a new manager, COPY A USER from an existing person in the same role so the checkboxes carry over instead of being clicked one by one.

flowchart TD
  A[Manager opens a screen] --> B{Is the matching permission set to 1}
  B -- No --> C[Screen hidden or read only]
  B -- Yes --> D{Does user level meet the gate}
  D -- No --> C
  D -- Yes --> E[Manager can act]
  E --> F{Is the target at or below their level}
  F -- No --> C
  F -- Yes --> G[Change is saved]

Reading the checkboxes as object pairs plus a handful of standalone gates makes the whole matrix easier to reason about. Decide what each role truly needs, then enable only those boxes and leave the rest at their safe default.

These checkboxes are the heart of the team setup we cover in the users and groups guide, and they build directly on user levels. On VICIfast you get a managed dialer where these permissions are yours to configure from the first minute. See our pricing page to spin one up in under a minute.