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

​Services Changes

Following a critical PHP security advisory affecting installations worldwide, we temporarily restricted public access to some of our backend services while carrying out necessary upgrades. Access has now been restored, and the affected services are operating normally. The Vodia PBX itself does not use PHP and was not directly affected. We explain what happened, the changes to legacy licensing and TLS support, and why customers running older PBX versions should contact us for upgrade guidance.

October 22, 2026

How to submit a support ticket in the Vodia Help Center

Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.

October 21, 2026

Make the Switch: The Vodia PBX Migration Tool

Switching phone systems doesn’t have to mean rebuilding everything from scratch. The Vodia PBX migration tool imports key configuration data from backups, including extensions, ring groups, queues, desk phones, and basic auto-attendant settings. Built into the Vodia Admin Portal, it guides administrators through the import process and reduces repetitive manual work, whether you’re moving 10 extensions or 1,000. Explore what transfers, what needs manual setup, and how the built-in tool reduces repetitive work when moving to Vodia.

October 15, 2026