Role-based access
Give IT, accounting, and compliance each exactly the access their role needs.
Not every person who needs some access to your phone system should have all of it. A team leader might need to manage their queue but should not be able to change billing settings. An accountant might need to view call records but should not be able to edit user accounts. A compliance officer needs to export logs but does not need to touch the call flows. Role-based access in Voxbi lets you draw these lines precisely, at the level of individual users, so each administrator sees and can change only what their role requires.
Permissions are configured per user from the Voxbi Cockpit. The Permissions tab on each user record controls what that person can do across telephony, outgoing calls, presence, call recording, and administrative functions. This means access is set intentionally rather than being all-or-nothing, and you can adjust it any time without creating a separate account.
When you'd use role-based access
An IT manager needs full administrative access but the department head only needs to manage their team's call queue, log in and out of it, and view the queue's performance. Give each person what they need and nothing more.
A compliance or finance team member needs to view call history and export logs for regulatory reporting. Grant read access to reporting without exposing call flow or user configuration settings.
A multi-site business where regional managers can see and edit users and extensions in their own location but should not be able to change system-wide settings or access other sites' configurations.