A model only appears here once its provider has a configured key. A provider with no key configured shows no models at all, so a missing model is often a missing key rather than a missing approval.
Approve and unapprove models
Every available model has an approval toggle. Approving a model adds it to the catalog people can pick from in the composer and to the pool Auto Route selects from. Unapproving it removes the model from both, without touching any thread history that already used it.Set a default
A default is the model used when nobody has chosen one explicitly. You can set a default at three scopes:1
Organization
Sets the workspace-wide default. This applies to anyone who doesn’t have a more specific default set for them.
2
Department
Sets the default for everyone in a department, overriding the organization default for that group.
3
Person
Sets the default for one individual, overriding both the department and organization defaults for them.
Force a default
Turn on Force for a default to stop the people it applies to from picking a different model in the composer. With force on, that scope’s default is the only model available to them, regardless of what else is approved in the catalog. Use this when a team needs to stay on one model rather than choosing per thread.Allow or deny personal model connections
A separate setting controls whether people can connect a personal model provider of their own and use it inside Sidekick instead of the workspace’s models. Turn it off to keep every thread on workspace-approved models only.Where to go next
Choosing a model
What the model picker and Auto Route look like for the people using Sidekick.
How models are chosen
How Auto Route and the approved catalog decide which model handles each turn.