Multi-Tenant

To support multi-tenancy, we created one digital employee per each tenant and can customize the prompt configuration, tool configuration, and MCP configuration at creation or runtime from each tenant. This approach allows us to make our digital employee generic.

Overview

Multi-tenancy enables a single Digital Employee Pipeline deployment to serve multiple tenants, each with their own customized configuration. This approach:

• Reduces infrastructure costs

• Simplifies maintenance

• Allows tenant-specific customization

• Maintains data isolation

Configuration Types

Prompt Configuration

Prompt configuration means we can configure the placeholders in the agent prompt (instruction), because sometimes we need to add placeholders to our prompt.

Here is an example of a prompt (instruction) with placeholders:

**A3.2.6 Find matched experience**
- Check if detected_sister_companies list is not empty.
- If there is at least one match in detected_sister_companies:
 - **A3.2.6.1** Send confirmation email (HTML) via MCP Gmail:
   - Use `google_mail_send_email` tool
   - To: candidate email; CC: {sister_company_email_cc}// Some code

{sister_company_email_cc} is the placeholder that needs to be replaced at runtime.

Tool Configuration

Tool configuration is the configuration for the tool that will be consumed by the agent. Agent tools need an input to run the tool. For example, the audio_transcription tool needs a Prosa API key. In this case, we can configure which API key we will use for a specific tenant.

MCP Configuration

MCP configuration is similar to tool configuration, but this works for MCP. For example, MCP Google Mail needs a GL Connector API key to be able to send emails to specific recipients. We can configure that key for a specific tenant.

Implementation

When creating a digital employee for a specific tenant, you can customize:

1. Prompt Placeholders — Replace tenant-specific values in prompts

2. Tool Credentials — Provide tenant-specific API keys and configurations

3. MCP Credentials — Configure MCP authentication per tenant

Example

# Create digital employee for tenant A
digital_employee_tenant_a = (
    DigitalEmployeeBuilder()
    .set_name("Claudia")
    .set_job(
        instruction="You are a helpful assistant for {company_name}",
        prompt_config={"company_name": "Tenant A Corp"}
    )
    .set_tool_config({"prosa_api_key": "tenant_a_key"})
    .set_mcp_config({"google_mail": {"x_api_key": "tenant_a_mail_key"}})
    .build()
)

# Create digital employee for tenant B
digital_employee_tenant_b = (
    DigitalEmployeeBuilder()
    .set_name("Claudia")
    .set_job(
        instruction="You are a helpful assistant for {company_name}",
        prompt_config={"company_name": "Tenant B Inc"}
    )
    .set_tool_config({"prosa_api_key": "tenant_b_key"})
    .set_mcp_config({"google_mail": {"x_api_key": "tenant_b_mail_key"}})
    .build()
)

Benefits

• Isolation — Each tenant has their own configuration and data

• Customization — Tenant-specific prompts, tools, and MCPs

• Scalability — Easy to add new tenants without code changes

• Flexibility — Configure at creation or runtime

Next Steps

• Learn more about Advanced Examples for complex multi-tenant scenarios

• Explore Advanced Configuration for detailed implementation guides