Tech

Administrators

Published on:

January 29, 2013

With snom ONE expanding into the cloud, the need for multiple administrators became evident. The new system now includes three distinct roles: the "super administrator," who retains full control over the PBX; the "system administrator," who shares many privileges but cannot alter super administrator accounts; and the "domain administrator," who manages specific domains without impacting account licenses. This new structure eliminates the need for sacrificing accounts for administrative purposes, and it clarifies roles. Additionally, the "login as" option has been removed, making it clear which role each user has within the system.

With snom ONE moving more and more into the cloud, we needed to address an old problem. There are usually several persons taking care of a system, but giving all of them the same username and password is a bad idea, - just like giving everyone the master key for a building. As employees join and leave companies, they must have their own credentials for logging into the system.

So we finally added multiple administrators. There are now three levels:

The “super administrator” is what we know from before. This person has full control over the PBX, including managing other administrators. When upgrading to 5.0.4, this account will stay the same.

The “system administrator” is similar to the super administrator, but cannot create, change or delete the super administrator or other system administrator accounts. There can be many system administrators, each one of them with their own password.

The “domain administrator” is similar to what was previously known as domain administrator permission of an extension. Those domain administrators can be set up in the domain properties by the system or super administrators, and each domain can have multiple domain administrators.

The point here is the domain administrators don’t count against account licenses. This was a problem with the previous concept, as usually one account had to be sacrificed for administration purposes - now system administrators don’t count against the license.

This also explains why the “login as” selection box has disappeared from the login screen, since the role each account has is clearly defined.

Latest Articles

View All

The New Vodia Partner Portal and Partner Program

The new Vodia Partner Portal and Partner Program provide a streamlined, self-service way for partners to license, sell, and deploy Vodia PBX solutions more efficiently. Shaped by partner feedback, the portal brings license management, partner levels, pre-qualified leads, marketing resources, and access to professional services into one place. Partner certification unlocks progression beyond onboarding, while a welcome package rewards partners at first login.

February 26, 2026

Continued Growth in the Global VoIP Marketplace

VoIP adoption continues to grow as enterprises and SMBs move away from legacy phone systems toward cloud-based communication that supports remote and hybrid work. Market forecasts show sustained expansion driven by cost efficiency, flexibility, and unified communications, while modern PBX platforms evolve to deliver scalable, reliable voice services with advanced features such as video, integrations, and AI-ready capabilities.

February 25, 2026

Cisco IP Phone Series 6800, 7800 and 8800 with the Vodia PBX

Cisco IP Phone Series 6800, 7800, and 8800 devices running Multiplatform (MPP / 3PCC) firmware can be used with the Vodia PBX in SIP-based environments. Supported models span entry-level, mid-range, and advanced devices commonly deployed in enterprise and service provider scenarios. Cisco-provided MPP firmware is used, with firmware versions and upgrades managed through the PBX after initial onboarding, supporting both on-premises and cloud deployments.

February 19, 2026