Sonata

Documentation · For administrators

Models

Models is where you choose the engine your agents run on: which provider powers the organization, whose key it uses, and which model new agents start with. It is the first area of Policy and access.

The model connection and whose key

Choose whether your agents run on Sonata managed models or your organization’s own provider key. Bring your own key and it is validated with the provider before it is stored, encrypted at rest, and never shown again; what you see afterward is a masked hint and the active source, never the secret. With your own key, inference runs under your organization’s own provider agreement and data boundary. You can switch back to managed, replace the key, or remove it from the same card at any time.

The default model

Set the model new agents start with. The built-in Sonata agents follow it too: they carry no model of their own, so each new conversation with one runs the default in force that day. An agent with an explicitly chosen model keeps it, and existing conversations always keep the model they started with, so a default change is never a silent rewrite of past work. When no default is set, the system flagship applies.

How to

Both controls are super admin only; org admins see them read-only.

Bring your own provider key

  1. Under Model connection, select Bring your own key.
  2. Paste your Anthropic API key and select Verify and save. The key is checked with Anthropic before it’s stored, encrypted at rest, and never shown again.
  3. Switch to managed, Replace key, or Remove key from the same card at any time.

Set the default model

  1. Under Default model, pick from the list and it saves.
  2. New agents start on it; existing agents and running conversations are untouched.

All documentation · Everything above describes the product as it ships today. If something here doesn’t match what you see, tell us.

← Back to documentation