> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eolasflow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise

> White-label branding, sub-organization management, and BYOK for agencies and resellers

Enterprise features let agencies and resellers white-label the platform, manage client organizations, set custom pricing, and bring their own API keys. Navigate to **Enterprise** in the Manage section to access these features.

<Note>
  Enterprise features require an Enterprise subscription plan. Contact [sales@eolasflow.ai](mailto:sales@eolasflow.ai) to upgrade.
</Note>

## Enterprise Dashboard

The Enterprise overview page gives you a high-level view of your reseller operation:

* **Sub-Organizations** — Total number of client orgs you manage
* **Credits Allocated** — Combined credits distributed to all sub-orgs
* **Branding Status** — Whether white-label branding is active and published
* **Quick Links** — Jump directly to Branding, Sub-Organizations, and Rates configuration

Use this page as your starting point before diving into individual sub-org management.

## White-Label Branding

Replace all EolasFlow branding with your own across the entire dashboard for your users.

<Steps>
  <Step title="Navigate to Branding">
    Go to **Enterprise → Branding** in the Manage section.
  </Step>

  <Step title="Set Company Name & Tagline">
    Enter your **Company Name** and **Tagline**. Your brand replaces "EolasFlow" throughout the dashboard for all users in your sub-orgs.
  </Step>

  <Step title="Upload Logo">
    Upload your **Logo** (PNG, JPEG, SVG, or WebP — max 2 MB). Your logo appears in the sidebar, outgoing system emails, and the login screen.
  </Step>

  <Step title="Upload Favicon">
    Upload a **Favicon** to replace the browser tab icon. Square images (32×32 or 64×64 px) work best.
  </Step>

  <Step title="Configure Color Theming">
    Set a **Primary Color** and **Accent Color**. These are applied across the entire dashboard UI for your sub-org users.
  </Step>

  <Step title="Configure Email Settings">
    Set the **Sender Name**, **Support Email Address**, and **Reply-To Address** used in all system emails sent on your behalf (call summaries, invites, alerts).
  </Step>

  <Step title="Preview & Publish">
    Use the live **Preview** to see exactly how the branding looks before making it visible to users. When satisfied, click **Publish**.
  </Step>
</Steps>

<Tip>
  Always use the preview before publishing. Check the sidebar, email headers, and login screen to make sure logos and colors look correct at all sizes.
</Tip>

<Note>
  You can reset to EolasFlow defaults at any time using the **Reset to Defaults** button. This does not delete your uploaded assets — you can re-publish them later.
</Note>

## Sub-Organization Management

Sub-organizations let you give each client their own fully isolated workspace. Perfect for agencies managing multiple clients under a single Enterprise account.

<Steps>
  <Step title="Navigate to Sub-Organizations">
    Go to **Enterprise → Sub-Organizations**.
  </Step>

  <Step title="Create a Sub-Org">
    Click **Create Sub-Org**, enter the organization name, and invite the initial admin by email.
  </Step>

  <Step title="Admin Accepts Invite">
    The invited admin receives an email and sets up their account. They become the owner of that sub-org.
  </Step>

  <Step title="Sub-Org is Ready">
    The sub-org is now an independent workspace. The admin can invite their own team members and start building.
  </Step>
</Steps>

Each sub-org is completely independent:

* **Own resources** — Assistants, VoiceFlows, contacts, conversations, and phone lines are isolated per sub-org
* **Inherited branding** — Sub-orgs automatically use your published white-label branding
* **Data isolation** — Members invited to a sub-org only see that org's data — never other clients' data
* **Separate billing** — Each sub-org draws from its own allocated credit balance

## Credit Management

Credits flow from your parent organization's pool down to each sub-org's individual balance.

### How Credit Allocation Works

1. Your parent org holds the master credit pool (purchased via the Usage page)
2. You allocate portions of that pool to individual sub-orgs
3. Sub-orgs consume credits from their own allocation as calls are made
4. The parent org dashboard shows each sub-org's remaining balance and consumption

### Allocating Credits

<Steps>
  <Step title="Open the Sub-Org">
    Go to **Enterprise → Sub-Organizations** and click on the sub-org you want to fund.
  </Step>

  <Step title="Add Credits">
    Click **Add Credits**, enter the amount to transfer, and add an optional description (e.g., "March allocation").
  </Step>

  <Step title="Confirm Transfer">
    Confirm the transfer. Credits move immediately from the parent pool to the sub-org balance.
  </Step>
</Steps>

<Tip>
  Set up low-balance alerts for each sub-org so you're notified before a client runs out of credits mid-campaign. Monitor sub-org usage from the parent dashboard on a weekly cadence.
</Tip>

## Rate Overrides

Set custom per-component rates for each sub-org to control your reseller margins. Rates are defined per direction (inbound and outbound) and per AI component.

| Component    | Description                                  |
| ------------ | -------------------------------------------- |
| **Platform** | Base platform fee per minute of call time    |
| **STT**      | Speech-to-text transcription cost per minute |
| **LLM**      | Language model inference cost per minute     |
| **TTS**      | Text-to-speech synthesis cost per minute     |

### Setting Rates

1. Go to **Enterprise → Sub-Organizations** and open a sub-org
2. Click the **Rates** tab
3. Set custom rates for each component and direction (inbound / outbound)
4. Use the **Markup** field to add a percentage on top of the base rate — this becomes your margin
5. Select the sub-org's **Currency** — exchange rate conversion is applied automatically

<Warning>
  Rate changes apply to future calls only. They are not applied retroactively to calls already completed or currently in progress.
</Warning>

## Provider Restrictions

Control which AI providers and platform features each sub-org can access. Start restrictive and open up as clients grow.

<AccordionGroup>
  <Accordion title="AI Pipeline Restrictions">
    Limit which voice pipeline modes the sub-org can use:

    * **OpenAI Realtime** — GPT-4o native audio pipeline
    * **Gemini Live** — Google's native audio pipeline
    * **Custom** — Modular STT + LLM + TTS pipeline

    Restricting to a single pipeline simplifies support and keeps costs predictable.
  </Accordion>

  <Accordion title="LLM Provider Restrictions">
    Control which language models the sub-org's assistants can use:

    * OpenAI (GPT-4o, GPT-4o mini, etc.)
    * Groq (Llama 3.3, etc.)
    * Gemini (Flash, Pro)

    Restrict to providers you have negotiated rates for or have BYOK keys configured.
  </Accordion>

  <Accordion title="TTS Provider Restrictions">
    Control which text-to-speech voices are available to the sub-org:

    * ElevenLabs
    * Cartesia
    * Google TTS
    * OpenAI TTS

    Limit to providers included in your rate overrides to avoid unexpected costs.
  </Accordion>

  <Accordion title="Resource Limits">
    Set hard limits per sub-org:

    * **Phone Numbers** — Maximum phone lines the sub-org can purchase
    * **VoiceFlows** — Maximum VoiceFlow (campaign) configurations

    These limits prevent a single sub-org from over-consuming shared resources.
  </Accordion>
</AccordionGroup>

<Tip>
  Start with conservative restrictions when onboarding a new client. As you understand their usage patterns, you can open up providers and increase limits from the Enterprise dashboard.
</Tip>

## BYOK (Bring Your Own Keys)

Use your own provider API keys instead of EolasFlow's shared pool. When BYOK is active, the corresponding component cost is zero — you pay the provider directly at your negotiated rate.

<Steps>
  <Step title="Navigate to API Keys">
    Go to **Organization → General** and scroll to the **API Keys** section.
  </Step>

  <Step title="Add Provider Keys">
    Click **Add Key** for the providers you want to configure. Supported providers:

    | Provider   | Use                            |
    | ---------- | ------------------------------ |
    | OpenAI     | LLM + TTS + Realtime pipeline  |
    | Deepgram   | STT                            |
    | ElevenLabs | TTS                            |
    | Groq       | LLM                            |
    | Gemini     | LLM + Live pipeline            |
    | Cartesia   | TTS                            |
    | Sarvam     | STT + TTS (regional languages) |
    | Pinecone   | Knowledge base vector storage  |
  </Step>

  <Step title="Verify Key">
    Paste your API key and click **Verify**. EolasFlow tests the key and confirms it is valid before saving.
  </Step>

  <Step title="BYOK is Active">
    Once saved, calls using that provider draw from your key. The component cost for that provider drops to zero in your credit usage.
  </Step>
</Steps>

<Note>
  BYOK requires an Enterprise plan. Keys are stored encrypted and are never displayed in full — only the last 4 characters are shown after saving.
</Note>

<Tip>
  BYOK is especially valuable for high-volume sub-orgs. Negotiating direct rates with OpenAI or ElevenLabs at scale can significantly reduce your per-call cost compared to the platform's shared rates.
</Tip>

## Best Practices

* **Start with one sub-org** — Test the complete flow (create, brand, allocate credits, run a call) before onboarding real clients
* **Set conservative provider restrictions initially** — Open up access as you understand each client's needs
* **Use rate markup for healthy margins** — Set markup per component so every call contributes to your reseller margin
* **Monitor sub-org usage weekly** — Catch unusual spikes early before a sub-org's balance runs out
* **Keep branding consistent** — Upload high-resolution logos (at least 200×200 px for the logo, 64×64 px for the favicon) to avoid blurry assets across screen sizes

## Next Steps

<CardGroup cols={3}>
  <Card title="Organization Settings" icon="building" href="/guides/organization">
    Configure your parent org, team members, and Twilio credentials
  </Card>

  <Card title="Usage & Credits" icon="credit-card" href="/guides/usage">
    Purchase credits and monitor consumption
  </Card>

  <Card title="Phone Lines" icon="phone-volume" href="/guides/phone-lines">
    Purchase and manage phone numbers for your sub-orgs
  </Card>
</CardGroup>