Overview

Your Bolna Organization is the central hub for all your voice AI resources. It acts as a top-level container for your team members, voice agents, billing information, API keys, and overall settings. Proper organization management is key to scaling your operations securely and efficiently. Within an organization, you can manage access for different team members, monitor usage across all your agents, and configure security policies that apply to your entire team.

Managing Team Members

You can invite new members to your organization and assign them roles based on their responsibilities. This ensures that team members only have access to the resources they need to perform their jobs.
  • Invite Members: Organization Admins can invite new users via email from the ‘Members’ tab in the organization settings.
  • Assign Roles: Each member is assigned a role that dictates their level of access and permissions within the organization.

Roles and Permissions

Bolna uses a simple two-role system to manage access control within your organization.
  • Admin: Has full, unrestricted access to the organization. Admins can manage billing, invite or remove members, create and delete agents, and manage all API keys. They have complete control over all settings.
  • Member: Has limited access designed for operational tasks. Members can edit existing agents, update prompts, and view analytics. They can create and manage their own API keys but cannot access API keys belonging to the admin or other members. Members are restricted from performing any delete operations (e.g., deleting agents or other members).

Usage & Billing

The Billing tab provides a complete overview of your subscription, plan details, and usage metrics like total call minutes and number of active agents. You can view invoicing history and manage your payment methods here.
The organization’s balance is shared across all users. All usage from both Admin and Member accounts is deducted from this single, centralized balance.

API Keys

Both Admins and Members can generate API keys for programmatic access. However, access is scoped based on role:
  • Admin Keys: Have full permissions and can perform any action via the API.
  • Member Keys: Are restricted to the same permissions as the Member role. They can be used to edit agents but cannot perform delete actions. Members can delete and create their own API Keys while not having access to the admins or other member’s keys.