Settings

Planned

Tenant configuration: SLA targets, KB repo, ITSM adapter selection, oncall roster.

Not built yet

This page is on the roadmap. Below is what already works that covers the same job.

What you can do today

Tenant config lives in the database (tenants.config JSONB column) and can be edited via scripts/update_tenant_config.py. The agent reads SLA targets, KB repo, and ITSM adapter selection from there at startup.

Environment variables (LIVEKIT_URL, DATABASE_URL, OPENAI_API_KEY, etc.) live in Railway. There's no plan to expose those in the UI — they should change via the Railway dashboard, with audit trail.

Target availability

After the v1 page sweep and Clerk auth land — settings without auth would be a footgun.