Cap the model every stage of a playbook uses
A playbook with several stages runs each stage at the model tier its seniority asks for. Max model puts a ceiling over all of them for one task: a stage that asks for more runs at the cap, and a stage that asks for less keeps its own tier. Use it to keep a large playbook run cheap, or to try a playbook on a lower tier before you trust it.
Who can do this: Requires the org admin role (Org Owner or Admin). Running a playbook also needs Playbooks on your organization's plan; see Run a playbook on a task.
- On the board, select New task, then describe the work. See Start a task.
- In the size menu (it shows Task at first), pick Playbook, then pick your playbook from the menu. A playbook that can't run yet is greyed out, with the reason under its name.
- Select Advanced. On a playbook with several stages the Persona field goes away, because each stage brings its own, and the model field is named Max model. Hover the label for Caps every stage's model.
- In Max model, pick the highest tier any stage may use: Max, High, Standard or Low. Inherit, the default, sets no cap: each stage runs at its own tier.
- Select Go. The task starts, and each stage runs at its own tier or the cap, whichever is lower.
- To change the cap later, open the task, select its Task tab, then Advanced, change Max model and select Save.
A playbook with a single stage shows the usual Model field instead. There it pins the tier outright, as on any task; see Choose the agent and account a task runs on.
Members who aren't Org Owners or Admins don't see the field, so a playbook task they start runs every stage at its own tier.
Related
- Choose the agent and account a task runs on: the Model field on an ordinary task, and the other pins under Advanced.
- Run a playbook on a task: pick a playbook and start it.
- Set how senior a playbook stage is: the tier each stage asks for in the playbook itself.