What Search Lead Ignore Group Restrictions does

By default, VICIdial keeps a manager inside their lane. When someone searches for a record on the admin lead search page, they only see leads that belong to campaigns their user group is allowed to touch. That is usually what you want in a multi-team shop where each team should not browse another team's customers. Search Lead Ignore Group Restrictions is the setting that lifts that boundary for a specific account.

What changes when you set it to 1

Set this to 1 and the user can search for Lead records throughout the entire system, not just within the Campaign entries their User group permits. The default is 0, disabled, which keeps the normal group-scoped view. This is the difference between a supervisor who can only audit their own team's leads and a back-office account that needs to find any record regardless of which team loaded it.

There is a second, easy-to-miss effect: the same flag also allows modifying those leads on the administrative lead modification page. So you are not just widening what they can find, you are widening what they can edit. If the account also has lead-editing rights, this combination becomes powerful fast, and you should treat it as a sensitive grant.

Think of it as removing the campaign fence. Without the flag, a manager's view of the Lead list universe is bounded by their group's Allowed Campaigns: searches, filters, and edits all respect that boundary. With the flag set to 1, that fence comes down and every record in the database is reachable from the admin search and modify pages. Nothing else about the account changes, but its reach over customer data widens dramatically.

The prerequisite people trip over

You cannot enable this setting on an account unless you yourself belong to a user group that has ALL CAMPAIGNS selected in its Allowed Campaigns section. In other words, only a truly system-wide administrator can hand out a system-wide lead search. If the option appears greyed out or refuses to save, this is almost always the reason: the editing account is scoped to a subset of campaigns and therefore cannot grant a privilege it does not fully hold itself.

How the search scope is decided

flowchart TD
  A[Manager runs a lead search] --> B{Ignore Group Restrictions set to 1}
  B -->|no| C[Limit results to allowed campaigns of user group]
  B -->|yes| D[Return leads from entire system]
  D --> E[Allow edits on admin lead modify page]
  C --> F[Edits limited to allowed campaigns]

This is a sensible guardrail rather than an arbitrary restriction. It prevents an admin who is themselves scoped to one team from quietly granting themselves, or a colleague, a view into every other team's customers. If you genuinely need to give someone system-wide lead search, the right move is to first place them in a user group with all campaigns allowed, then enable the flag from an account that already holds that full scope.

When to grant it

Reserve this for a small number of trusted operators: account managers who pull records across every team, compliance staff handling DNC (do not call) removals, or a senior admin who consolidates Lead list cleanup. For most supervisors, leave it at 0 so the natural group scoping does its job and one team never accidentally edits another team's customers. Because the flag also opens up editing on the admin lead modification page, it pairs closely with the level-based modify rights; granting both to the same person effectively makes them a system-wide Lead owner for editing purposes, so apply it deliberately. The broader model of who sees which campaigns is laid out in our VICIdial users and groups multi-team guide.

This setting controls finding and editing existing leads; the separate levels that govern field-by-field editing are worth knowing too. We cover them in the Modify Leads permission levels post.

If you are building out a fresh dialer and want these multi-team boundaries clean from the start, a managed VICIdial server is online in under 40 seconds. Check the pricing to spin one up.