Skip to main content

Scribe settings

Route/authoring/scribe/settings PreviewScribe previewscribe

Scribe Settings — "Configure the AI provider Scribe uses to generate documentation." — is the tenant's LLM configuration. The LLM Provider card holds everything; the values are stored by the Suite's LLM gateway, and the bulk generation jobs read them.

FieldChoices
ProviderAnthropic (default), OpenAI, Azure OpenAI, Local (Ollama). A provider the gateway cannot route to yet is labelled (coming soon) and disabled — "X is coming soon. Choose Anthropic or OpenAI to save."
ModelThe provider's models — for Anthropic, Claude Opus, Sonnet and Haiku; for OpenAI, the GPT-4o family
API KeyA password field with Reveal / Hide. A stored key shows "A key ending last4 is stored. Enter a new one to replace it." — the key itself is never shown again
Temperature0 to 1 in steps of 0.05, default 0.3, labelled Precise, Balanced, Creative

Without a key for the chosen provider: "Add an API key for X so Scribe can generate."

Save settings (Saving…, then "Settings saved.") stores the provider, model and temperature, and — only when you typed one — the new API key, encrypted. Reset to defaults returns the form to Anthropic at 0.3.

The design surfaces' AI assistant is separate: it talks to the Ollama server the operator configures, not to this provider.

For operators: keys are encrypted with the authoring service's SPIRE_CREDENTIAL_ENCRYPTION_KEY; budgets, usage and the audit log are per tenant through the Spire API.