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

Configuring Emergency Alerts and Notifications with V70 of the Vodia PBX

V70 introduces emergency alerts and notifications designed to ensure critical events are not missed and responses happen immediately. Alerts can be triggered directly by users, delivered across multiple channels including phones, email, mobile apps, and SMS, and can automatically initiate calls to predefined numbers. Administrators have full control over how alerts are configured, enabling consistent, reliable handling of incidents across real-world, multi-tenant environments.

March 26, 2026

Vodia V70: WhatsApp Business Calling and Messaging Integration

Vodia V70 integrates WhatsApp Business calling and messaging directly into the PBX, allowing businesses to manage voice and customer conversations from a single platform. With native SIP integration, WhatsApp calls are routed to extensions, queues, or IVRs without middleware, reducing complexity and eliminating the need for additional gateways. Combined with support for messaging, dashboards, alerts, and AI voice agents, V70 brings greater control, scalability, and flexibility to real-world communication environments.

March 24, 2026

Vodia PBX V70: New Admin Interface, AI Voice Agents, and Scalable Multi-Tenant Performance

Vodia PBX V70 introduces a redesigned admin interface, multi-core scalability supporting more than a thousand concurrent calls per server, and integrated AI voice agents for both inbound and outbound communication. Reusable AI templates make automation easier to deploy, while snapshots and centralized provisioning reduce operational risk. With custom dashboards, emergency alerts, and WhatsApp Business integration, V70 provides greater control and flexibility for real-world deployments.

March 19, 2026