Do not look for a guaranteed “Remove AI” button beside each member in Notion’s People settings. Current documentation describes controls for models, spending and specific features—not the per-person AI add-on seat removal described in older tutorials. First decide whether you want to reduce credit spending, restrict a feature, or prohibit all AI use for particular people.
Official documentation checked October 14, 2026. This guide does not claim that a credit limit disables every AI feature.
Define Exactly What Must Be Restricted
Write down the intended outcome before changing a setting. “This member must not spend premium-model credits” is different from “this member must not use any AI” or “AI must not access this confidential page.” Those requirements need different controls and different verification.
Current Business and Enterprise plans include AI capabilities. An administrator should not assume that removing a separate paid AI seat is possible simply because an old article calls AI an add-on. Review Notion’s current AI settings and your actual contract.
Manage Premium-Model Spending
The documented path for owners and admins is Settings → Notion AI → Usage. Review the workspace’s enabled premium models, default credit limit and member or group limits. Follow Notion’s model and member-credit guide when setting the values supported by your workspace.
This is cost control, not complete removal of AI access. Notion explicitly says that members reaching a premium-model credit limit can continue using models included in their plan. Therefore, a successful ordinary AI response does not prove that the credit limit failed.
Restrict a Model or a Specific Feature
An owner or admin can switch off a premium model in the workspace model controls. This affects that model for the workspace, not just one member. Custom Agents have separate model controls; do not assume the personal Agent setting applies to them.
For web search, review Settings → Notion AI and the documented web-search and external-request confirmation settings. The security guide describes their scope. Disabling web search is not the same as blocking workspace AI or revoking page permissions.
If You Need a Complete Per-Person AI Prohibition
The reviewed official sources do not establish a universal People-menu switch that revokes every AI feature for a selected member while leaving all other access unchanged. Do not promise that outcome or treat a missing control as a browser bug.
Ask the workspace owner or Notion support which controls are available for your plan and exact requirement. Supply the feature names, member roles and scope, without sending confidential page contents. Obtain confirmation of what the control covers before relying on it for a security or employment policy.
Do not demote someone to guest, remove them from groups or delete their account merely to experiment with AI restrictions. Those actions can disrupt legitimate collaboration and are not equivalent to an AI-specific control.
Verify the Intended Effect
- Record the original setting and the approved change.
- Have the affected member test the specific feature with harmless data, in the correct workspace.
- Check the relevant usage or credit view. Separate a blocked premium model from an allowed included model.
- Test an unaffected member when the change is intended to be selective.
- Document any remaining access rather than calling the whole account “AI disabled.”
Keep Content Permissions Separate
If the concern is a confidential document, review who can access that document and connected source. Changing a spending limit does not change content permissions. Conversely, removing access to one source does not remove every AI capability from the member.
The safe result is a verified control with a clearly stated scope. If a required complete prohibition is not supported, escalate that policy decision rather than substituting a weaker setting and claiming success.