Organization management

Access

If you wish to use the organization feature, contact our support to request access.

Overview

Organizations in VH represent fully isolated tenants. Each organization operates as an independent unit and cannot access or interact with resources belonging to other organizations.

This isolation applies across all platform resources, including workspaces, calendars, phone numbers, meta connections, SIP trunks, and email configurations.

---

Creating Organizations

Organizations can be created from the Organizations tab in the left-hand sidebar. This tab is visible only when organization management has been enabled for your account.

When creating an organization, you may optionally define a monthly credit limit. This allows you to control and cap usage at the organization level. Credit limits can also be configured when creating sub-organizations.

After creating your first organization, you can access it via its assigned subdomain. For details, see Accessing an Organization.

---

Organization Structure (Nesting)

VH supports unlimited organization nesting, allowing you to create hierarchical structures of arbitrary depth and breadth.

For example:

• You create an organization called Acme Corp

• Within Acme Corp, you create a sub-organization called Acme Europe

• Within Acme Europe, you create another sub-organization called Acme Netherlands

This hierarchy forms a tree structure:

• Each organization can access itself and all of its descendants

• Organizations cannot access parent organizations or sibling organizations

This ensures strict separation while enabling structured delegation.

---

Whitelabeling and Domains

Each organization can fully customize its platform experience through whitelabeling and custom domains.

By default, every organization is assigned a subdomain in the following format: org-69b98226722606501ee16654.voicehub.dataqueue.ai

Organizations may also configure custom domains via the Domains tab. If you configure a custom domain, the entire VoiceHub platform will be available at your custom domain using your organization.

Whitelabeling capabilities include:

• Custom branding across the platform interface

• Custom login page styling

• Custom email configuration for invitations

Access to whitelabeling and domain configuration is restricted to the organization owner.

---

Accessing an Organization

Organizations can be accessed via their assigned subdomain or a configured custom domain.

When accessing an organization:

• A custom-branded login page is presented

• All actions are scoped to the selected organization

• Resources created or modified (such as agents or phone numbers) belong exclusively to that organization

Users authenticate using the same credentials across all organizations they have access to.

• Users who signed up via Google will receive an auto-generated password upon creating their first organization

• Users who signed up via email and password will continue using the same credentials across all organizations

---

Users and Roles

Inviting Users

Users can be invited to an organization by assigning them a role (either predefined or custom). Invitations are sent via email and include login credentials as well as the organization URL.

Role Inheritance

Roles are inherited downward through the organization hierarchy.

For example:

• If a user is an Admin in Acme Corp, they will automatically have Admin access in Acme Europe and Acme Netherlands

Access Rules

• Users in a parent organization can access all of its child organizations

• Users in a child organization cannot access parent organizations

Permission Scope

A user’s role determines their permissions across:

• Organization-level actions

• Agent-level actions within that organization

User Management

Organization members can be viewed in the Members tab. Removing a user will immediately revoke their access to the organization.

---

Platform Behavior Within an Organization

When operating within an organization, the platform behaves consistently with the standard VH experience, with a few key differences:

• All agents are visible to all organization members with the View Agents permission

• The “Shared agents” concept does not apply

• All resources are accessible to all members within the organization

• The “Collaborators” tab is not present in workspaces

This model simplifies collaboration within an organization by ensuring full visibility for all members with the View Agents permission.

---

Billing

All usage across organizations is billed to the root account, which owns the top-level (parent) organization.

For example:

• If you own Acme Corp, you are billed for usage incurred by:

  • Acme Corp

  • Acme Europe

  • Acme Netherlands

  • Any additional nested organizations

This centralized billing model ensures a single point of financial responsibility.

---

Credit Consumption

Organizations can monitor usage through the Credit Consumption tab.

Each organization can view:

• Its own credit usage

• The credit usage of all its child organizations

This provides full visibility into how resources are consumed across the hierarchy.