What the Delete Users, Lists and Campaigns permissions control

VICIdial keeps deletion behind its own set of permission checkboxes, separate from the rights that merely let someone edit. A Campaign is the dialing configuration that ties leads, agents, and dispositions together, and removing one is far more destructive than editing it. The same goes for users and lists: a careless delete throws away work you cannot click undo on. This post explains the Delete family so you know exactly what each box hands over and to whom you should hand it.

The three big delete options

Delete Users, when set to 1, lets a manager remove other accounts from the system, but only accounts of equal or lesser user level than their own. Delete Lists lets the user remove VICIdial lists, the containers that hold a batch of leads. Delete Campaigns lets the user delete entire campaigns. All three default to 0, off, so deletion is something you opt into account by account rather than a side effect of any broader manager role. If a manager swears they cannot find a delete button, the answer is almost always that the matching Delete box is unchecked on their record.

• Delete Users: removes accounts at or below your user level.
• Delete Lists: removes Lead list records, separate from Modify Lists.
• Delete Campaigns: removes whole campaigns, separate from Modify Campaigns.

Why delete is split from modify

Editing a record is reversible: change a field back and you are fine. Deleting a campaign or a list can throw away the link to historic call data and the configuration an Agent relied on. By forcing Delete to be its own checkbox, VICIdial lets you build a manager who can tune campaigns and lists all day yet can never remove them, which is the safer default for most teams. The pattern continues across the matrix, with Delete In-Groups, Delete Scripts, and Delete Filters each split from their modify counterparts. The split is not bureaucracy for its own sake; it is the difference between an annoying mistake and an unrecoverable one.

Choosing what to grant

Keep the Delete boxes on a short list of senior managers and leave them off for everyone else. Most day-to-day work needs only the Modify rights. A practical habit is to disable instead of delete wherever possible: set a finished campaign to inactive rather than removing it, so the reports stay intact, and only delete once you are certain the data is no longer needed. When you do grant Delete, pair it with a clear rule about who is allowed to use it and a quick check before each removal.

It also helps to remember that the level rule only applies to Delete Users, not to lists or campaigns. Anyone with Delete Lists can remove any list, and anyone with Delete Campaigns can remove any campaign, regardless of who created it. There is no per-object owner check on those two the way there is on accounts. That makes Delete Lists and Delete Campaigns blunter instruments than Delete Users, and it is one more reason to reserve them for the handful of administrators who understand the full picture of what a given list or campaign is feeding.

flowchart TD
  A[Role needs delete rights] --> B{Removing accounts}
  B -- Yes --> C[Grant Delete Users]
  A --> D{Removing lists}
  D -- Yes --> E[Grant Delete Lists]
  A --> F{Removing campaigns}
  F -- Yes --> G[Grant Delete Campaigns]
  C --> H[Keep delete to senior staff]
  E --> H
  G --> H

Delete rights are some of the most powerful gates in the users and groups guide. For the account side specifically, see how to delete a VICIdial user. On a VICIfast Single tenant box you control who holds these permissions with no shared admins outside your team. Visit our pricing page to launch one in under a minute.