Tenant Provisioning

How to create a new tenant — automated provisioning creates the namespace, database records, configuration, and demo data in a single step.

What provisioning does

Creating a new tenant is a single action that sets up everything needed for a working namespace. No manual database edits, no config file creation, no separate steps. One command (or one form submission in the backoffice) creates:

Namespace in the vector index for document storage
Database records in all platform tables (tenant config, equipment registry, user assignments)
Model configuration with namespace-specific templates
Domain ontology initialized with common equipment terminology
Demo data (optional) — mock queue jobs, telemetry readings, and service history so the tenant has a populated dashboard immediately

Provisioning from the backoffice

The Provisioning page in the backoffice provides a form-based interface:

Field	Description
Namespace	URL-safe identifier for the tenant (e.g., `acme_marine`). Cannot be changed after creation.
Display Name	Human-readable name shown in the UI (e.g., "Acme Marine Services")
Manufacturer	The equipment manufacturer this tenant services
Equipment Models	Comma-separated list of equipment models to register
Enable Demo Data	Toggle to auto-generate mock DMS data for the dashboard

Click "Provision Tenant" and the system creates everything in sequence. Progress is shown as each step completes. The entire process takes under 10 seconds.

Provisioning from the CLI

For scripted or batch provisioning:

.venv/bin/python scripts/provision_tenant.py \
    --namespace acme_marine \
    --display-name "Acme Marine Services" \
    --manufacturer "Acme" \
    --equipment-models "Model A, Model B" \
    --demo-data

The --demo-data flag generates realistic mock data: 5-8 queue jobs with varied statuses, telemetry readings for each equipment model, and a basic service history. This is useful for demos, sales presentations, and evaluation environments.

What happens next

After provisioning, the tenant needs content. The typical next steps are:

Upload documentation — Go to Upload and Ingestion and upload the manufacturer's service manuals, owner's manuals, and any TSBs
Run auto-onboarding — The self-serve onboarding pipeline can generate a complete pipeline configuration from a single PDF
Invite users — Add technicians and administrators on the Team page
Verify quality — Run an evaluation to confirm answer quality before going live

Demo mode

When demo data is enabled during provisioning, the tenant dashboard is immediately populated with realistic content:

Queue jobs with varied statuses (pending, in progress, completed) and realistic equipment, complaint text, and fault codes
Telemetry readings with gauge values for each registered equipment model
Service history entries spanning the last 90 days

Demo data is clearly labeled in the UI and does not interfere with real data once documents are ingested and real jobs come in through DMS integration or manual creation.

Demo mode is designed for three scenarios:

Sales demos — Show a populated dashboard to prospects without needing their actual data
Evaluation environments — Let potential customers explore the full workflow before committing content
Internal testing — Verify frontend behavior with realistic data during development

Customer Onboarding Guide — the complete playbook from contract to production
Upload and Ingestion — adding documents after provisioning
Team Management — inviting users to the new tenant