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

Vodia Version 70.2 - Run Multiple Licenses on the Same Virtual Machine

V70.2 introduces more flexible licensing for multi-tenant PBX deployments by allowing service providers to assign prepaid licenses directly to tenants within a postpaid environment. Once assigned, the tenant uses the prepaid license independently, and the underlying postpaid license no longer counts that tenant. This gives MSPs and hosted PBX providers more flexibility in how they structure customer licensing while continuing to operate tenants on shared infrastructure, reducing operating costs and simplifying large-scale multi-tenant deployments.

May 26, 2026

Austrian MSP my Tweak Telekom GmbH Completes Two Vodia PBX Installations

Austrian MSP my Tweak Telekom completed two Vodia PBX deployments in Vienna, helping Pension Suzanne modernize its hotel communications and enabling New Business Verlag GmbH to upgrade from a legacy on-premise phone system to a hosted cloud PBX. The projects demonstrate how businesses can modernize legacy telephony infrastructure, improve operational flexibility, preserve existing hardware investments, and deliver better communication experiences with cloud-based unified communications.

May 21, 2026

Vodia PBX V70 Webinar: Admin Interface, Analytics, AI, and Multi-Tenant Performance - Recording Now Available

Watch the Vodia PBX V70 webinar on demand and explore the latest improvements in the Vodia PBX, including the redesigned admin interface, built-in PBX analytics, AI voice agents, automation, and scalable multi-tenant performance. The session also covers snapshots, centralized provisioning, emergency alerts, skills-based routing, and integrations with Jitsi Meet and WhatsApp Business in real-world deployment environments.

May 19, 2026