Platform
ScaiWave ScaiGrid ScaiCore ScaiBot ScaiDrive ScaiKey Modellen Tools & Services
Oplossingen
Organisaties Ontwikkelaars Internet Service Providers Managed Service Providers AI-in-a-Box
Kenniscentrum
Ondersteuning Documentation Blog Downloads
Bedrijf
Over ons Onderzoek Vacatures Investeren Contact
Inloggen

Permissions

ScaiDial has two layers of access: module permissions for tenant-wide administration and call control, and extension roles for what a person may do with particular extensions. Everything is scoped to the caller's tenant.

Module permissions#

Granted to users, groups or API keys by a tenant admin. Tenant and partner admins hold every module permission automatically. Every admin route checks its permission; having ScaiDial enabled for the tenant is not enough.

Permission Allows
scaidial:trunks:manage Trunks, registration status, numbers (DIDs), network info, tenant policy (voicemail transcripts, phone limits, call recording, call language), tenant music-on-hold playlists and the default
scaidial:extensions:manage Extensions, phone logins (read, rotate), extension roles, forward rules, all voicemail in the tenant
scaidial:dialplan:manage Dialplans and rules (IVR menus, announcements)
scaidial:calls:observe Active calls and call history, and controlling calls: hang up, hold, transfer, attended transfer, merge, conference controls, speak
scaidial:extensions:own The personal-settings MCP tools (DND, forwarding, ring timeout) on extensions the caller owns
scaidial:recordings:read List and play every call recording in the tenant (each play is logged)
scaidial:recordings:manage The same, plus delete recordings and start/pause/resume/stop any call's recording
scaidial:calls:place, scaidial:calls:place_autonomous Reserved for placing outbound calls from agents

Typical roles: a receptionist or supervisor gets scaidial:calls:observe; someone who edits routing without seeing carrier credentials gets scaidial:dialplan:manage; an auditor gets scaidial:calls:observe (note that it includes call control).

Extension roles#

The end-user portal (/my/dial, /me/…), ScaiWave and personal music-on-hold playlists use roles on individual extensions instead of module permissions. The user a wave extension belongs to is its owner; admins grant other roles with POST /extensions/{id}/grants, to a user or a group.

Role Can
owner Everything below, plus change the extension's personal settings (DND, ring timeout, greeting, forward rules, caller ID, music-on-hold playlist) and place calls from it
manage Manage another person's line: in ScaiWave the same as owner; in /my/dial read and delete its voicemail and see its calls
answer Answer its calls; read its voicemail (in ScaiWave)
observe See it and its calls; read its voicemail (in ScaiWave)

A user without any role sees an empty /my/dial that points them to their tenant admin.

Examples#

Operation Needs
POST /trunks, GET /trunks/{id}/registration scaidial:trunks:manage
GET /extensions/{id}/sip-account scaidial:extensions:manage
POST /dialplans/{id}/rules scaidial:dialplan:manage
GET /calls/active, POST /legs/{id}/consult, POST /calls/merge scaidial:calls:observe
GET /voicemail (all mailboxes) scaidial:extensions:manage
GET /me/voicemail owner or manage on the extension
POST /me/click-to-call owner of the source extension
POST /moh/playlists any user (personal); admins create tenant playlists

API keys#

An API key acts with the roles and module permissions of the identity it belongs to (its owner, or the user or group it is assigned to). For full ScaiDial administration, issue the key to a tenant admin, or to an identity granted scaidial:trunks:manage, scaidial:extensions:manage, scaidial:dialplan:manage and scaidial:calls:observe.

Updated 2026-10-14 00:46:57 View source (.md) rev 12