You want Notion AI to generate content that matches your team’s tone, terminology, and formatting rules across every page. Notion AI Custom Instructions let you define a single set of style guidelines that applies to all AI responses in a workspace. This article explains how to set up Custom Instructions, what rules they can enforce, and how to avoid common pitfalls that make AI output inconsistent.
Key Takeaways: Setting Workspace-Wide AI Style Rules
- Settings & Members > Workspace > Notion AI: The only location where Custom Instructions can be added for all workspace members.
- Custom Instructions text box: Enter tone, vocabulary, and formatting rules that Notion AI applies to every AI-generated response.
- Preview pane: Shows a sample output after you type an instruction, letting you test the rule before saving.
What Notion AI Custom Instructions Do and What You Need First
Notion AI Custom Instructions act as a persistent system prompt that prepends every AI request in the workspace. When a member asks Notion AI to write a summary, draft a meeting note, or rewrite a paragraph, the AI first reads the custom instructions and then generates the response. This ensures consistent style across all users without each person having to repeat the same rules.
Before you can set Custom Instructions, you need three things. First, you must be a workspace owner or admin. Second, the workspace must have an active Notion AI subscription. Third, you need a clear set of style rules written in plain English. Examples include “Use active voice” or “Capitalize product names as follows: Notion, Notion AI, Workspace.”
Custom Instructions are workspace-wide, meaning every member who uses Notion AI in that workspace will follow the same rules. There is currently no per-page or per-user override. If a member needs different instructions for a specific project, they must manually edit the prompt each time.
Steps to Add and Test Custom Instructions
- Open the Workspace Settings menu
Click the left sidebar gear icon to open Settings & Members. Then click Workspace in the left panel. - Locate the Notion AI section
Scroll down the Workspace settings page until you see the Notion AI heading. Click the arrow or expand button next to it to reveal the Custom Instructions pane. - Write your style rules in the text box
Type each rule on a new line. Be specific. For example: “Use the Oxford comma. Write dates as Month Day, Year. Avoid jargon. Use bold for key terms.” You can enter up to approximately 1000 characters. - Preview the output
Below the text box, a preview pane shows a sample AI response based on your instructions. The default preview prompt is “Write a short paragraph about team collaboration.” If the output looks correct, proceed. If not, edit the instructions and wait for the preview to update automatically. - Save the instructions
Click the Save button at the bottom of the pane. The instructions become active immediately for all workspace members. No one needs to refresh or restart Notion.
Testing Custom Instructions on a Real Page
- Open any Notion page
Navigate to a page where you want to test the AI. Press the spacebar or type a forward slash to bring up the command menu. - Trigger an AI action
Type “AI” in the command menu and select an action such as Improve Writing, Summarize, or Draft. The AI will apply the Custom Instructions before generating the response. - Review the output for rule compliance
Check whether the AI followed your rules. For example, if you asked for active voice, confirm the sentence structure. If a rule was missed, go back to the Custom Instructions pane and rephrase the rule.
Common Mistakes When Writing Custom Instructions
Instructions Are Too Vague
A rule like “Write professionally” is too broad. The AI may interpret professional as formal, technical, or concise depending on the context. Replace vague terms with concrete examples. Instead of “Write professionally,” write “Use full sentences. Do not use slang. Avoid first-person pronouns.”
Contradictory Rules
If you write “Use short sentences” and “Include detailed explanations” in the same instruction set, the AI will produce inconsistent results. Review your rules for logical conflicts. Remove or merge rules that cannot coexist.
Rules That Conflict with Notion AI Defaults
Notion AI has built-in defaults for tone, length, and structure. For example, by default it uses active voice and avoids repetition. If your Custom Instructions repeat a default behavior, they have no effect. Focus on rules that differ from the baseline, such as specific vocabulary or formatting.
No Testing After Changes
Every time you edit the Custom Instructions, test the preview and a real page. The preview pane updates automatically, but the live AI behavior may differ slightly. Run at least two different AI actions after saving to verify consistency.
Notion AI Custom Instructions vs Per-User Prompting
| Item | Workspace Custom Instructions | Per-User Manual Prompting |
|---|---|---|
| Scope | All members in the workspace | Individual user only |
| Setup effort | One-time, admin only | Repeated every time |
| Consistency | High — same rules for everyone | Low — depends on user memory |
| Flexibility | Low — no per-project override | High — any rule for any task |
| Maintenance | Centralized edits | No central control |
Custom Instructions are best for teams that need uniform brand voice, legal disclaimers, or formatting standards. Per-user prompting works better for individual tasks or projects with unique requirements. You can combine both approaches: set workspace-wide rules for basic style, and let users add extra context in their prompt for specific tasks.
After you save your Custom Instructions, run a quick audit of AI-generated content for one week. Check if the rules are being applied correctly and if any team member has feedback about missing or overly strict rules. Adjust the instructions as needed and communicate changes to the team. For advanced control, consider adding a rule that tells the AI to ask for clarification when a request is ambiguous, such as “If the prompt is unclear, ask the user for more details before generating text.”