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

Using service flags in V70 of the Vodia PBX

V70 of the Vodia PBX introduces flexible service flags that help organizations automate call routing, scheduling, queue management, announcements, and communication workflows throughout the day. Service flags can be configured manually or automatically to control how calls are handled during business hours, after hours, holidays, or special events. They can also be chained together for more advanced routing logic and integrated with external calendars such as Google Calendar to support dynamic scheduling and operational flexibility across business environments.

May 12, 2026

Communication Systems: Finally Catching Up to Modern Technology or Still Stuck in the Past?

Business communication systems have evolved rapidly, but many organizations are still dealing with fragmented tools, limited visibility, and growing operational complexity. As more platforms and channels are added, clarity often decreases, making it harder to manage workflows, respond in real time, and maintain control. A modern approach requires consolidating systems, improving visibility, and reducing noise to create a more efficient and manageable communication environment.

May 6, 2026

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

Explore Vodia PBX V70 in a live webinar, featuring a detailed walkthrough of the redesigned admin interface, built-in PBX analytics for real-time visibility and control, AI voice agents, automation workflows, and scalable multi-tenant performance, along with key capabilities such as snapshots, centralized remote provisioning, emergency alerts, and integrations including Jitsi Meet and WhatsApp Business, followed by a live Q&A session with the presenters.

April 30, 2026