Set your Notion agent model roster before the default decides for you

Your Notion workspace now has model controls, and the default is already choosing for you. The fix is a one-page roster that says which models are allowed, who owns them, and when to revisit. On September 9, 2026, Notion added model controls that let workspace owners manage AI model access for Notion Agent and Custom Agents independently and pick a default for Custom Agents.

The controls are available on Business and Enterprise plans. Custom Agents arrived in February 2026 as autonomous teammates that handle recurring work across Notion, Slack, Mail, Calendar, Figma, Linear, and custom MCP servers. Custom Agents began as a no-cost public beta until May 3, 2026, and from May 4, 2026 they used Notion Credits and were limited to Business and Enterprise plans. Early testers created more than 21,000 Notion Custom Agents, Ramp runs more than 300, and Remote reported saving 20 hours per week on task routing.

The setting is at Settings, Notion AI, General, Model controls. Notion built the controls to keep costs predictable and support compliance needs.

The default is already a decision

Most teams do not choose the default. They notice it after the first invoice, the first client question, or the first agent run that should not have happened. A model roster prevents that by making the choice visible: what is allowed, what runs by default, what is excluded for sensitive work, and who owns the change.

Put the roster on one page

The roster is one page, short enough for a founder to read before a meeting and an ops lead to update after one. Two surfaces need separate lines because the controls let Business and Enterprise workspace owners manage model availability for Notion Agent and Custom Agents independently.

The default line matters because the Custom Agent default runs when no one makes a choice, so it should be the one you would defend in a client call. Sensitive work needs a compliance rule, so the client-data line should exclude models that are too new, too expensive, or too hard to explain. The reason, owner, and trigger lines keep the page reviewable without digging. A reason that survives a review is usually about cost, compliance, or quality.

Make the roster checkable in one minute

Keep the roster in the same place as the setting. If it is in a doc that nobody opens, it will not be used. The list below is the one-page version. Each item is testable in a minute because it asks for a name, a choice, or a trigger.

• Allowed models for Notion Agent: write the exact names available in that control; Notion provides access to frontier models named Opus 5, GPT-5.6 Sol, and Kimi K3, and the picker shows speed, intelligence, and cost indicators.
• Allowed models for Custom Agents: write the exact names available in that control, separate from the Notion Agent list.
• Default Custom Agent model: the controls include a default-model setting, so name the model that runs when no one chooses one and note why it is the default.
• Client-data exception: state which model is allowed when an agent touches client data, and which models are excluded for compliance.
• Reason: record the cost, compliance, or quality reason in one sentence.
• Owner: name the person who can change the roster and who must approve a change.
• Revisit trigger: set a date or event that forces a review, such as a Business or Enterprise plan change, a new frontier model, or a credit spike.

The Custom Agent Insights API gives Business and Enterprise users a usage feed for credit spend, finished runs, and status, with controls to switch agents on or off or cap them. Use it as the verification.

After the roster is written, check it against the actual setting. If the setting and the page disagree, the page is wrong until someone fixes it. Then tell the team where the roster lives.