Skip to main content
A model policy decides which models can be used at all. Instead of ticking models one by one, you write rules, such as “only these providers” or “nothing above this price”. They are checked every time someone sends a message, so a model released tomorrow is decided by today’s rules. The policy applies everywhere a model is chosen: the model picker, every message, and Auto, which only ever picks from models the policy allows.
Model policy and the per-message spending limit are included on the Business, Business Elite and Enterprise plans.

​
Two levels: organization and project

A project’s rules can only narrow the organization’s rules, never widen them. If a project rule would allow something the organization’s rules don’t, you’re told before you can save.

​
The rules you can set

Leave a rule empty and it doesn’t restrict anything. A model has to pass every rule you set.

​
Review before you save

Select Review changes before saving. Parlé shows what the change would do:
  • Whether a project rule would widen the organization’s rules, and which organization rule it conflicts with.
  • Whether any project or personal conversations would be left with no usable model.
  • How many conversations active in the last 30 days are on a model the change would newly stop, per project.
Save policy is offered only once the review has run and nothing in it blocks the change.
When a saved change stops a model that recent conversations were using, the members of those projects are notified straight away (“A model policy change affects your conversations”), so nobody finds out by being refused mid-task.

​
What members see

​
A blocked model in the picker

A model your policy stops stays in the model picker, greyed out and marked blocked by an admin. It doesn’t silently disappear. If someone opens a conversation that was last on a blocked model, it reopens on the project’s default model and says why.

​
A message a rule stops

If someone sends on a model the policy doesn’t allow, the message isn’t sent. Instead they see:
  • Why: an admin has restricted that model. It never says which rule, or who set it.
  • A way to carry on: Continue with … on one suggested model, the lowest-priced model the policy allows that can still do the job (including using tools, if the conversation has used them). One click resends the same message in the same conversation. That send is checked again, so a policy that changed in between still applies.
  • Who can change it: a link to the relevant policy for an admin who can lift it. A Project Admin stopped by an organization rule gets Ask an organization admin to change the policy, which sends a request to the Org Admins’ Requests queue.

​
Per-message spending limit

A per-message spending limit caps what one message may cost. A message whose estimated cost is over the limit is refused before any model is called, so one very long conversation can’t spend a month’s budget in a single answer. The lower of the two applies. When a message is refused, the notice says it isn’t a budget problem, names the limit, and points to what helps: compact the conversation, or start a new one. When a project limit refused it, the notice also offers Request a higher limit, which an Org Admin can approve. Each limit is set in a currency: the project’s budget currency, or one the Org Admin chooses (US dollars by default). See Currencies.
The per-message limit is separate from project budgets and spending caps. Budgets cap total spend over a period; the per-message limit stops a single message from being unexpectedly expensive.

​
If your plan changes

If your organization moves to a plan without model policy:
  • Your rules and limits keep applying. Losing the feature never loosens a control you set.
  • You can remove them, but not add new ones or raise a limit.
  • Nothing is deleted.

Model Selection

Enable models for your organization and set the default.

Auto

Let Parlé pick the model for each conversation, inside these rules.