System & Access

The System & Access section contains administrative settings related to platform operations, security, and integrations.

Available Sections

SMTP

Configure SMTP settings used for outgoing platform emails, including invitations, password reset emails, MFA codes, billing alerts, and system notifications.

SMTP Host

Type: stringHostname of the outgoing mail server.Example:

smtp.gmail.com

SMTP Port

Type: numberPort used for SMTP communication.Common values:

465
587
25

Connection Options

Use Secure Connection

Type: booleanEnables SSL/TLS encrypted connection to the SMTP server.

Disable TLS Certificate Validation

Type: booleanDisables TLS certificate verification.

Use this option only for testing or internal SMTP servers.

Authentication

SMTP Username

Type: stringUsername used to authenticate with the SMTP server.Example:

platform@example.com

SMTP Password

Type: passwordPassword or application-specific password used for SMTP authentication.The value is hidden in the interface.

Email Sender Settings

Mail From

Type: stringSender address used for outgoing emails.Must be a valid email address or use the following format:

Name <email@example.com>

Examples:

no-reply@example.com

Monobot <no-reply@example.com>

Notification BCC

Type: stringOptional email address that receives copies of outgoing platform notifications.Example:

bcc@example.com

Support Email

Type: stringEmail address displayed or used for support-related communication.Example:

support@example.com

Test Settings

Use Test Settings to verify SMTP connection, credentials, and email delivery configuration before saving or using the setup.

SMTP configuration is required for system emails such as invitations, password resets, MFA codes, billing alerts, and notification templates.

Members

Manage platform users and their access to the current tenant.The Members section provides a list of all users associated with the selected tenant and allows administrators to manage user access.

Members List

The table displays all users currently registered within the tenant.

First Name

Type: stringUser’s first name.Example:

John

Last Name

Type: stringUser’s last name.Example:

Doe

Email

Type: stringUser’s email address used for authentication and notifications.Example:

john.doe@example.com

User Management

Administrators can use the Members section to:

View all tenant users
Verify user information
Manage platform access
Monitor active users
Review organization membership

Access Control

Manage role-based permissions and advanced platform access settings.The Access Control section allows administrators to define what actions users can perform within the platform by assigning privileges to specific roles.

Bot Change Control

Enable switching bots to Production mode

Type: booleanAllows users assigned to the selected role to publish bots to the Production environment.When enabled:

Bots can be promoted from Draft to Production
Published bots become available for live usage
Future changes require a commit message before publishing

After a bot is published, every subsequent change requires a commit message describing the modification.

RBAC Settings

Role-Based Access Control (RBAC) determines which resources a role can access and what actions can be performed.

Role

Type: selectSelect the role whose permissions you want to configure.Example:

Tenant Administrator
Agent Manager
Operator
Viewer

Privileges

Configure permissions for each platform entity.Each entity supports the following permissions:

Permission	Description
Can Read	View records and information
Can Update	Modify existing records
Can Delete	Remove records
Can Create	Create new records

Available Entities

Organization

Manage organizations and tenant-level configuration.

Interaction

Manage interaction history, transcripts, and conversations.

Usage

Access usage statistics and consumption reports.

Agent

Manage AI agents and bot configurations.

Billing

Access invoices, subscriptions, and payment information.

Language

Manage supported languages and localization settings.

Phone

Manage phone numbers and telephony resources.

Sub Organization

Manage child organizations and organizational hierarchy.

Template

Manage notification, email, and message templates.

Bot Advanced Access

Grant advanced permissions for bot configuration and administration.

Change Voice Processor

Type: booleanAllows users to modify the Voice Processor used by the bot.Examples:

OpenAI Voice
ElevenLabs
Azure Speech

Change STT Processor

Type: booleanAllows users to change the Speech-to-Text (STT) engine.Examples:

Deepgram
OpenAI Whisper
Google Speech-to-Text

Change LLM

Type: booleanAllows users to modify the Large Language Model used by the bot.Examples:

GPT-4o
Claude
Gemini

Full Access to Integrations

Type: booleanProvides access to the Integrations tab and allows management of connected services.Examples:

Google Calendar
SMTP
SIP
Altegio
WooCommerce

Read Interaction Metrics

Type: booleanAllows viewing interaction analytics and performance metrics.Examples:

Conversation statistics
Call duration
Resolution rate
Usage metrics
Interaction transcripts

Changes made in Access Control take effect immediately for all users assigned to the selected role.

SIP

Configure SIP authentication and network access settings for inbound SIP and SIPS connections.

IP Whitelist

Type: listDefines which IP addresses are allowed to connect to the platform through SIP or SIPS.Supported formats:

214.8.230
214.8.*
214.8.230-88.214.8.240
db8::1

Examples

Single IP

88.214.8.230

Allows connections only from the specified IP address.

Wildcard Range

88.214.8.*

Allows all IPs within the specified subnet.

IP Range

88.214.8.230-88.214.8.240

Allows all addresses within the defined range.

IPv6 Address

2001:db8::1

Allows a specific IPv6 endpoint.

If no IP addresses are configured, connections are allowed from any IP address.

SIP Username

Type: stringUsername used for SIP Digest Authentication and SIP REGISTER requests.The connecting SIP client must provide this username when authenticating with the platform.

Example

sip_test_user

SIP Password

Type: passwordPassword associated with the SIP Username.The platform validates incoming SIP authentication requests using this password.

Example

StrongPassword123!

Store SIP credentials securely and rotate them regularly to prevent unauthorized access.

Authentication Flow

SIP provider or PBX sends a SIP REGISTER or INVITE request.
Platform validates the supplied SIP Username.
Platform verifies the SIP Password using Digest Authentication.
If an IP Whitelist is configured, the source IP is validated.
Connection is accepted only when all validation checks pass.

SIP Username and SIP Password are required only when SIP Digest Authentication is enabled on the call initiator side.

Call Attached Data

Configure custom key-value pairs that are attached to interactions and can be consumed by external systems, integrations, APIs, or downstream workflows.Call Attached Data (CAD) allows you to expose interaction metadata in a structured format for third-party systems.

Field Name

Type: stringDefines the custom field key that will be included in the interaction payload.Field names should be unique and descriptive.

Examples

tenant_field_org_id
tenant_field_status
customer_id
ticket_number

Value

Type: variableDefines the interaction variable or system value that will populate the field.Values are selected from available interaction variables.

Examples

Organization ID

Interaction.organizationId

Stores the organization identifier associated with the interaction.

Interaction Status

Interaction.status

Stores the current interaction status.Examples:

active
completed
failed
transferred

Creating a New Field

Click New Field (+) to create an additional CAD entry.For each field:

Enter a unique Field Name.
Select a Value from the available variables.
Save the configuration.

Managing Existing Fields

Edit Field

Update either the field name or the mapped value.

Delete Field

Remove a CAD field using the delete icon.

Deleting a field removes it from all future interaction payloads but does not affect historical interaction data.

Example Configuration

Field Name	Value
tenant_field_org_id	Interaction.organizationId
tenant_field_status	Interaction.status

Example output:

{
  "tenant_field_org_id": "12345",
  "tenant_field_status": "completed"
}

Common Use Cases

CRM integration
Ticketing systems
Custom reporting
External workflow automation
Webhook enrichment
Customer data synchronization

Configured CAD fields are automatically attached to interactions and can be accessed by supported APIs and integrations.

API

Manage API keys used to authenticate external applications, services, and integrations with the platform.API keys provide secure access to platform APIs without requiring interactive user authentication.

Create API Key

Generate a new API key for a specific service or integration.

Key Name

Type: stringA human-readable name used to identify the API key.Choose a descriptive name that reflects its purpose.

Examples

Production SIP Integration
CRM Connector
Webhook Service
Analytics API

Service Type

Type: selectSelect the service or feature that the API key will be authorized to access.Example:

SIP

Additional options may be available depending on enabled platform features.

Generate

Creates a new API key using the specified name and service type.

The generated API key should be stored securely. Depending on your deployment, the full key may only be shown once.

API Keys

Displays all active API keys created within the tenant.

Name

Type: stringThe user-defined name assigned during key creation.Example:

Production SIP Integration

Creator Email

Type: emailEmail address of the user who generated the API key.Example:

admin@company.com

Created At

Type: datetimeDate and time when the API key was created.Example:

2026-01-15 14:30 UTC

Valid Until

Type: datetimeExpiration date of the API key.If no expiration policy exists, the platform may display an extended validity period.Example:

2027-01-15 14:30 UTC

API Key

Type: secretDisplays the generated API credential.Depending on platform configuration, keys may be partially masked for security purposes.Example:

sk_live_xxxxxxxxxxxxxxxxx

Delete

Type: actionRevokes and permanently removes the API key.After deletion:

API requests using the key will immediately fail
Existing integrations using the key must be updated
The key cannot be recovered

Deleting an API key immediately revokes access for all systems using that credential.

Typical Use Cases

SIP authentication
External integrations
Webhook authorization
CRM synchronization
Internal automation services
Custom API clients

Security Best Practices

Create separate keys for each integration
Rotate keys regularly
Remove unused keys immediately
Never share API keys publicly
Store credentials in a secure secrets manager

API keys inherit the permissions associated with the selected service and tenant configuration.

Changes made in System & Access settings can affect platform functionality, integrations, and user access.

​System & Access

​Available Sections

​SMTP Host

​SMTP Port

​Connection Options

​Use Secure Connection

​Disable TLS Certificate Validation

​Authentication

​SMTP Username

​SMTP Password

​Email Sender Settings

​Mail From

​Notification BCC

​Support Email

​Test Settings

​Members List

​First Name

​Last Name

​Email

​User Management

​Bot Change Control

​Enable switching bots to Production mode

​RBAC Settings

​Role

​Privileges

​Available Entities

​Organization

​Interaction

​Usage

​Agent

​Billing

​Language

​Phone

​Sub Organization

​Template

​Bot Advanced Access

​Change Voice Processor

​Change STT Processor

​Change LLM

​Full Access to Integrations

​Read Interaction Metrics

​IP Whitelist

​Examples

​Single IP

​Wildcard Range

​IP Range

​IPv6 Address

​SIP Username

​Example

​SIP Password

​Example

​Authentication Flow

​Field Name

​Examples

​Value

​Examples

​Organization ID

​Interaction Status

​Creating a New Field

​Managing Existing Fields

​Edit Field

​Delete Field

​Example Configuration

​Common Use Cases

​Create API Key

​Key Name

​Examples

​Service Type

​Generate

​API Keys

​Name

​Creator Email

​Created At

​Valid Until

​API Key

​Delete

​Typical Use Cases

​Security Best Practices

System & Access

Available Sections

SMTP Host

SMTP Port

Connection Options

Use Secure Connection

Disable TLS Certificate Validation

Authentication

SMTP Username

SMTP Password

Email Sender Settings

Mail From

Notification BCC

Support Email

Test Settings

Members List

First Name

Last Name

Email

User Management

Bot Change Control

Enable switching bots to Production mode

RBAC Settings

Role

Privileges

Available Entities

Organization

Interaction

Usage

Agent

Billing

Language

Phone

Sub Organization

Template

Bot Advanced Access

Change Voice Processor

Change STT Processor

Change LLM

Full Access to Integrations

Read Interaction Metrics

IP Whitelist

Examples

Single IP

Wildcard Range

IP Range

IPv6 Address

SIP Username

Example

SIP Password

Example

Authentication Flow

Field Name

Examples

Value

Examples

Organization ID

Interaction Status

Creating a New Field

Managing Existing Fields

Edit Field

Delete Field

Example Configuration

Common Use Cases

Create API Key

Key Name

Examples

Service Type

Generate

API Keys

Name

Creator Email

Created At

Valid Until

API Key

Delete

Typical Use Cases

Security Best Practices