Setting a Project Default Model
Each project can have a designated default model. When a member opens a new conversation in that project, the default model is pre-selected so they can start working immediately without choosing a model themselves. To set or change the default:1
Open Project Settings
Navigate to your project and click Settings in the project sidebar.
2
Select a default model
Under the Models section, open the Default Model dropdown and choose the model you want pre-selected for new conversations.
3
Save your changes
Click Save. New conversations started in this project will now open with that model active. Existing conversations are not affected.
Curating Allowed Models
Org admins can restrict which models are visible and selectable within any given project. This is useful when you want to steer a team toward cost-efficient models for routine work, enforce a specific provider for compliance reasons, or simply reduce decision fatigue by showing only the most relevant options.1
Open Project Settings
Navigate to the project and click Settings.
2
Go to the Models tab
Select the Models tab within Project Settings.
3
Disable models not needed for this project
Uncheck any models you want to hide from project members. Unchecked models remain enabled at the org level — they are simply not surfaced in this specific project.
4
Save
Click Save. The updated model list takes effect immediately for all members of the project.
Only org admins can curate the allowed models for a project. Project admins and members see only the models that have been enabled for their project.
Switching Models Mid-Conversation
You can switch to a different model at any point in an open conversation — mid-thread, mid-task, or after reviewing an initial response. To switch models:- Open the conversation you are working in.
- Locate the model selector in the toolbar at the top or bottom of the chat input area.
- Click the selector and choose a different model from the list.
- Continue typing your next message. The new model picks up from the current conversation context.
Switching models does not lose your conversation history. The new model sees the same thread from the beginning, so you can seamlessly continue a complex document review or multi-step analysis after changing models.
The model used to generate each individual message is recorded in the conversation thread and in your org’s usage log. This means you can audit exactly which model produced each response — useful for client billing transparency and for reviewing AI-assisted work product.