Setup, Permissions, and Compliance

Prepare roles, carrier accounts, webhook ownership, test controls, recording consent, and billing before enabling LeenOps telephony.

Treat telephony setup as an administrative change. It can alter carrier webhook destinations, create billable calls or number orders, and expose recordings or transcripts to Workspace members.

ResponsibilityRecommended owner
Carrier account, balance, routes, and emergency contactsTelephony administrator
LeenOps provider connection and default selectionWorkspace owner or administrator
Roles and recording accessSecurity or Workspace administrator
Test destinations and budgetProject owner
Recording notice, consent, and retentionLegal or compliance owner

Do not share API secrets in tickets, screenshots, chat, or documentation. Enter them only in the password fields under Settings > Telephony & Messaging.

Telephony Permissions

LeenOps roles can grant telephony actions separately. Owners and administrators normally have the required access; custom roles should receive only what their job requires.

Provider administration

PermissionAllows
telephony.provider.connectCreate, edit, or test a connection, including its credentials
telephony.settings.manageChange the default provider
telephony.provider.disconnectDisconnect a provider

Calling and call records

PermissionAllows
telephony.call.outboundPlace outbound calls
telephony.call.viewView call records within the granted scope
telephony.call.transferTransfer a supported live call
telephony.call.record.toggleStart or stop recording when the provider supports it
telephony.call.view_recordingsListen to call recordings
telephony.call.view_transcriptRead call transcripts

Phone numbers

PermissionAllows
telephony.phone_number.viewView synchronized numbers
telephony.phone_number.provisionSearch and submit a number order
telephony.phone_number.assignAssign a number to a member
telephony.phone_number.releaseReturn a number to the provider

Use custom roles to separate callers from telephony administrators. A sales representative usually needs outbound calling and own/team call visibility, not credential, purchase, or release permissions.

Pre-Production Checklist

  1. Create or identify a dedicated carrier API credential for LeenOps.
  2. Record the carrier account owner and support path outside LeenOps.
  3. Confirm allowed destinations, balance, concurrency, and trial limits.
  4. Assign the minimum Workspace permissions.
  5. Configure the provider's signed webhook URL.
  6. Use a controlled test destination in international E.164 format.
  7. Confirm provider status, call journal, duration, and linked CRM record.
  8. Test disconnect and recovery in a non-critical window.

Recording and Transcription

Recording availability is provider-specific. Before enabling it:

  • determine whether one-party or all-party consent applies in every country involved;
  • provide the required call notice;
  • document the lawful purpose and retention period;
  • restrict recording and transcript access with separate permissions;
  • include recordings and transcripts in access, export, and deletion procedures;
  • verify whether the carrier keeps an additional copy and for how long.

LeenOps documentation is product guidance, not legal advice. Your organization remains responsible for telecommunications, privacy, employment, and recording rules that apply to its calls.

Billing and Destructive Actions

  • The carrier bills calls, messages, and numbers to the connected account.
  • A Telnyx Confirm purchase action submits a billable number order.
  • Releasing a Telnyx number can make it permanently unavailable.
  • Connecting Zadarma can replace its single PBX call-notification URL.
  • Disconnecting Zadarma does not restore the previous carrier URL.

Require an explicit human review for number purchases, releases, provider cutovers, and production acceptance calls.