16. Settings

Settings is the control center for organization identity, access, billing, AI providers, branding, integrations, localization, BIQ Voice, assistant behavior, discount logic, and API keys.

Each settings tab saves its own area. Make changes deliberately because several settings affect public widget delivery.

For detailed operation of the high-impact settings areas, see Settings Deep Dive.

Settings Tabs

Tab	What you configure
Organization	Name, slug, production domain, staging URLs, locale, timezone, retention, source-domain rules, lead recipient, customer worker subdomain.
Team	Members, pending invites, and roles.
Plan & Billing	Plan, subscription state, invoices, and quota context.
AI provider	Provider settings, budget controls, and usage-related limits.
Branding	Widget colors, font, radius, text color, button color, powered-by badge where plan allows it.
Integrations	Embed snippets, customer domain state, crawler domain information.
Notifications	Operational notification settings and test delivery.
LLM visibility	Controls for AI crawler visibility and llms.txt-style exposure.
Embed	Touchpoint embed configuration and snippet handling.
Glossary	Terms that should be used consistently in generated answers and translations.
Translations	Planned locale and review behavior for translated BIQs. Translation Management comes later.
Brand Voice & Compliance	Style rules, banned patterns, answer structure, examples, prompt guidance, product recommendation settings, and SafeGuard config.
Assistant	Studio assistant access to aggregated organization data.
Discount codes	Discount-code behavior for recommendations and lead/conversion flows.
API keys	Server-side public read keys and scopes.

Organization

Organization settings control identity and delivery boundaries.

Important fields:

• organization name and slug,
• production domain,
• staging and test URLs,
• locale and timezone,
• trash retention,
• material aging threshold,
• official manufacturer domains,
• excluded competitor domains,
• behavior for BIQs without a source,
• default lead recipient,
• customer worker subdomain.

Changing the slug or production domain can invalidate existing embeds. After changing either, copy a fresh snippet from the Studio and test on production and staging.

Team

Use Team settings to invite users and manage roles. Role changes affect what a user can read, edit, publish, and configure.

Recommended practice:

• keep owner access limited,
• use admin for operational leads,
• use member for content work,
• remove unused invites,
• review team access before go-live.

Branding

Branding controls the public widget appearance:

• primary color,
• text color,
• button color,
• secondary color,
• font family,
• border radius,
• powered-by badge where plan allows it.

The preview shows how public answers will look. Always check contrast after changing text and button colors.

Integrations And Embed

Use these tabs to copy the embed snippet and verify delivery settings.

Check:

• correct touchpoint selected,
• correct mode,
• correct org-slug,
• correct touchpoint-slug,
• correct data-worker-url,
• production and staging origins allowed,
• customer worker subdomain connected if used.

See Embedding Touchpoints and Developers.

LLM Visibility

LLM visibility controls how Klariton exposes touchpoints to AI crawlers and agentic retrieval systems.

Use it to decide:

• whether a touchpoint should be visible to AI crawlers,
• which routes or generated files should be exposed,
• whether crawler visibility is intentionally enabled or disabled.

Disabling crawler visibility does not necessarily hide the normal widget from end customers. It affects AI crawler reach.

Glossary

Glossary terms help Klariton use names, product terms, and brand language consistently. Add terms that must not be mistranslated or paraphrased.

Examples:

• product family names,
• certifications,
• internal category names,
• spelling rules,
• terms that must remain in English.

Translations COMING SOON

Translation Management is planned for a later release. When available, translation settings define how BIQ translations are created and reviewed. A translation can become stale when the source answer changes or when SafeGuard updates the BIQ.

Planned workflow:

1. Enable required locales.
2. Generate translations.
3. Review engines or locales that require review.
4. Re-sync stale translations after source edits.
5. Test the touchpoint in every public locale.

Brand Voice & Compliance

This tab is one of the most important areas in Klariton. It affects generation, rewriting, SafeGuard, and chat behavior.

Configure:

• banned phrases or patterns,
• style rules,
• answer structure,
• golden examples,
• custom prompt guidance,
• product recommendation display rules,
• B-stock or excluded-product handling,
• stale BIQ regeneration behavior,
• Drift SafeGuard auto-scan config.

SafeGuard auto-scan is opt-in. It can run daily or weekly and can also check BIQs at creation time where enabled.

See Brand Voice & Compliance and SafeGuard.

Assistant

Assistant settings control whether the Studio assistant may access aggregated organization data.

Sources can include:

• reach and KPIs,
• BIQs and content state,
• personas,
• product catalog,
• material inventory,
• SafeGuard state.

The assistant is read-only. It can explain numbers and link to actions, but it should not edit, publish, or delete content.

API Keys

API keys allow server-side access to published touchpoint data.

Current public-read scope:

read_published

Rules:

• keep keys server-side,
• rotate keys when access changes,
• revoke unused keys,
• do not put keys into browser bundles,
• prefer least scope once more scopes exist.

See Developers.