Source
Models & processing location — found from sitemap — Leena AI
Checked for Leena AI on 3 Nov 2026
- Page
- https://docs.leena.ai/docs/model-configuration
- Checked
- 3 Nov 2026, 14:27 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:819ec48c9aaf44724139f19fa6a520b2f558ab2e6c39a8a3da43dd8bef7d9186
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Model levels Report an error
“LLMs are configured at two levels: the Master Orchestrator (MO), which governs the whole bot, and individual AOPs, which can either inherit the MO's model or override it.”
-
Default model Report an error
“The default configuration is OpenAI — GPT 5.5.”
-
Llm providers Report an error
“Provider Available models OpenAI GPT 6 Astra (New), GPT 6.1 Sol (New), GPT 5.6 Terra (New), GPT 5.5, GPT 4.1 (retiring) Azure OpenAI GPT 6 Astra (New), GPT 6.1 Sol (New), GPT 5.6 Terra (New), GPT 5.5, GPT 4.1 (retiring) Anthropic Opus 5.5 (New), Sonnet 5.5 (New), Sonnet 4.6, Opus 4.7 (retiring), Opus 4.6 (retiring), Opus 4.5 (retiring) Amazon Bedrock (Anthropic) Opus 5.5 (New), Sonnet 5.5 (New), Sonnet 4.6, Opus 4.7 (retiring), Opus 4.6 (retiring), Opus 4.5 (retiring)”
-
Effort setting Report an error
“Effort — Controls how thoroughly the model thinks before responding (Low / Medium / High). Higher effort improves reasoning quality on complex requests at the cost of response time. Default: Low. Available on every model except GPT 4.1.”
-
Priority processing Report an error
“Priority processing — Runs requests through a priority lane for faster, more consistent response times. Available on supported models only and Off by default where supported”
-
Aop inheritance Report an error
“By default, the AOP uses the Master Orchestrator's model configuration and follows it live — if an admin changes the Master Orchestrator's model, every inheriting AOP switches with it, with no action needed on the AOP.”
-
Aop override Report an error
“An overriding AOP stores its own full configuration (provider, model, and model settings) and is unaffected by Master Orchestrator changes.”
-
Model traceability Report an error
“Run History and the Debugging Console record the resolved provider and model for every run, so you can always trace which model handled a request.”
-
Retiring models Report an error
“Retiring model Providers Available until Automatically moves to GPT 4.1 OpenAI, Azure OpenAI 30 November 2026 GPT 5.6 Terra Opus 4.5 Anthropic, Amazon Bedrock 30 November 2026 Opus 5.5 Opus 4.6 Anthropic, Amazon Bedrock 30 November 2026 Opus 5.5 Opus 4.7 Anthropic, Amazon Bedrock 30 November 2026 Opus 5.5 Sonnet 4.6 Anthropic, Amazon Bedrock 30 November 2026 Sonnet 5.5”
-
Retirement auto migration Report an error
“Nothing breaks. Any Master Orchestrator or AOP still set to a retiring model automatically runs on its replacement — no action needed.”
-
Model benchmarks doc Report an error
“Use the Compare models link in the picker header to view benchmarking data before deciding. See LLM Model Benchmarks.”
Scores citing this record
- The Automation Lead Models & processing location
- The Automation Lead European sovereignty
- The Customer-Service Director Models & processing location
- The Customer-Service Director European sovereignty
- The Data Protection Officer Models & processing location
- The Data Protection Officer Agent capabilities & guardrails
- The Data Protection Officer European sovereignty
- The Head of IT Models & processing location
- The Head of IT European sovereignty
- The Skeptic Models & processing location
- The Skeptic Agent capabilities & guardrails
- The Skeptic European sovereignty
- The Works Council Member Data use, training & retention
- The Works Council Member Models & processing location
- The Works Council Member Agent capabilities & guardrails
- The Works Council Member European sovereignty