Custom Models
What custom models are for
A custom model defines reusable assistant behavior. It combines an LLM, a system instruction, and visibility rules.
What can be configured
A custom model can include:
- a name
- a description
- a category
- tags
- an LLM
- a default system instruction
- visibility
- team access
- a credential mode
When to use a custom model
A custom model is useful when the goal is to:
- keep a stable tone and behavior
- reuse the same instruction across several flows
- prepare a building block that will later be used inside a group model
Visibility and sharing
A model can be:
- private
- shared with teams
- public
Public visibility should be used only for models that are intentionally designed for broader reuse.
BYOK and the vault
When BYOK is used, the model can rely on a secret stored in the Vault. This makes it possible to use custom credentials without exposing them in the model configuration.
Good practices
- Keep the system instruction short and precise.
- Use the description to explain the intended use case.
- Use clearly differentiated names when several variants coexist.
- Review visibility carefully before making a model public.