What the Modify Phones, Servers and Statuses permissions cover

VICIdial breaks system administration into separate permissions so you can hand out only what each person needs. Three of them - Modify Phones, Modify Servers, and Modify Statuses - each open a specific cluster of admin sections. They overlap in places, so it helps to know exactly what each one covers before you assign them.

Modify Phones

Modify Phones gives the user access to edit three sections: phones, phone aliases, and group aliases. This is the permission for whoever manages your SIP peer endpoints, Hardphone (deskphone) entries, and Softphone definitions. If a person's job is adding new Extension records or fixing Phone registration details, this is the toggle they need and usually nothing more.

Modify Servers

Modify Servers is the broadest of the three. It unlocks servers, settings containers, system settings, system statuses, status categories, and QC status codes. This reaches into how the whole box behaves, so it is the most sensitive grant. Editing a Settings container or system settings can change call handling system-wide, which is why you reserve this for a genuine system administrator rather than a campaign manager.

Modify Statuses

Modify Statuses covers system statuses, status groups, status categories, CID groups, and VM message groups. This is the toggle for the person who defines what Disposition codes exist and how they roll up for reporting. Status groups bundle individual statuses together so reports can summarize outcomes cleanly, and VM message groups govern the voicemail recordings tied to those flows. Note the deliberate overlap: system statuses and status categories appear under both Modify Servers and Modify Statuses, so a status-only admin can shape outcome codes without touching server settings, while a server admin still has them too. That overlap is a feature, not an accident, because it lets you give a reporting lead just enough to maintain the taxonomy without ever exposing the broader server controls.

How the three split the admin surface

flowchart TD
  A[Modify Phones] --> A1[Phones]
  A --> A2[Phone aliases]
  A --> A3[Group aliases]
  B[Modify Servers] --> B1[Servers]
  B --> B2[Settings containers]
  B --> B3[System settings]
  B --> B4[System statuses]
  C[Modify Statuses] --> B4
  C --> C1[Status groups]
  C --> C2[CID groups]
  C --> C3[VM message groups]

How they relate to AGC Admin Access

These three give you fine-grained control over individual section clusters. If you instead want one account to reach a much wider range of astGUIclient screens in a single grant, that is what AGC Admin Access does, covered in the AGC Admin Access post. The granular toggles are the better choice when you want to keep telephony plumbing and status definitions in different hands.

Assigning them sensibly

Give Modify Phones to your phone provisioning person, Modify Statuses to whoever owns reporting taxonomy, and keep Modify Servers in the hands of one or two senior admins. Splitting them this way means a mistake in one area cannot cascade into another, and it keeps an audit trail of who could have changed what. A status admin who breaks a status group has not also touched your trunks; a phone admin who fat-fingers a SIP peer has not altered system settings. That isolation is the whole point of having three permissions instead of one.

These all live in the same permission matrix as the user-editing rights, so it helps to see how they slot in next to grants like Modify Users; we break that down in the Modify Users permission post. For the wider permission map across teams, see the VICIdial users and groups multi-team guide.

Running on a managed VICIdial box means the server itself is handled for you while you still control these permissions; provisioning takes under 40 seconds. See the pricing to launch one.