Routing policy
Rules selecting request perimeter by sensitivity and content type.
Role: deployment operator. These steps use the operator console. An ordinary hosted account exposes only its own keys and limits; request policy, protection-mode and masking changes from the operator.
Rules selecting request perimeter by sensitivity and content type.
This screen belongs to the Router deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.
Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.
Step-by-step actions
- Open Policy, enter your tenant and click Load. Preserve the previous JSON.
- Edit → Form, set a name, add a rule and move it ahead of broader rules.
- For example, choose block for RESTRICTED; use the organization-approved perimeter for other data.
- Set limits and retain fail_closed/block for strict protection.
- Preview evaluates the draft against history; Test policy evaluates a test decision. Save after review.
- Reload and repeat a synthetic request; use Version history → Roll back to restore a previous version.
Every control and its meaning
| Control / parameter | Values, units and effect |
|---|---|
| Tenant ID / Загрузить | Enter a tenant or * for global policy. Load reads server state; the top-bar tenant selection does not replace this input. |
| Правила периметра | Conditions use sensitivity/content_type; actions are route/block/reroute, with local/on_prem/external perimeter. First matching rule wins; arrows change priority. |
| Оптимизация / prefer | research_to_cheapest selects a cheap compatible research model; prefer is cheapest_relevant/fastest/balanced. Compatibility and perimeter still constrain selection. |
| reasoning_effort | none/low/medium/high; the request’s explicit value takes priority. Deeper reasoning increases budget and latency. |
| max_output_tokens / max_prompt_chars | Integers ≥ 0, with 0 meaning no cap. The first caps model output; the second rejects oversized prompts with 413. |
| Поведение при сбоях | on_classifier_unavailable: fail_closed/allow; on_injection_detected: block/flag; block_message is the client message. allow/flag weaken the relevant protection. |
| Форма / JSON | JSON exposes the full contract, including perimeter, perimeter_rules, when, request_limits and cost_optimization. Use the detailed reference for fields and ranges. |
Verify the result
Compare saved JSON with the new request ID’s action and reason. Route tests do not call an LLM; Chat tests the complete call. All 18 JSON fields are described in detailed settings.
Errors, disabling and reverting changes
For 422/invalid JSON, correct the field and preview again. Cancel discards the draft. Config reload rereads service files and differs from saving a tenant override; it is not a universal rollback.
2026-10-15 · Actual staging and an existing operator SSO session. Synthetic tenant/group only; the capture excludes credentials and the operator profile. The form does not establish application on every replica.
- mask_route
- Save
- fail_closed
2026-10-15 · Actual staging and an existing operator SSO session. Synthetic tenant/group only; the capture excludes credentials and the operator profile. The form does not establish application on every replica.
- mask_route
- Save
- fail_closed
2026-10-15 · Actual staging and an existing operator SSO session. Synthetic tenant/group only; the capture excludes credentials and the operator profile. The form does not establish application on every replica.
- mask_route
- Save
- fail_closed
Detailed security settings · Traffic analysis · FAQ · All application sections