Rules
Common Use Cases
- Status change alerts: notify the project manager when a task’s Status column changes to Blocked
- New submission notifications: email the intake coordinator whenever a new item is added to a request list
- Approval awareness: let the document owner know when a Status column reaches its final value
- Deadline ownership: notify the responsible person when the Due Date or Priority column changes
- Deletion monitoring: alert the list owner when items are deleted from a critical list
- Handoff notifications: email the person in a person column, such as Assigned To, when work moves to them
Benefits
- No-code automation: rules are built with fill-in-the-blank sentences, not workflow designers or expressions
- Targeted notifications: conditions ensure people hear about the changes that matter to them, not every edit
- Dynamic recipients: notifications can go to a named person or to whoever appears in a person column, such as Created By
- Lives with the list: rules belong to the list or library itself, so there is nothing separate to maintain
- Quick to change: rules can be turned off, edited, or deleted in seconds as processes evolve
- More precise than basic alerts: rules respond to specific columns and values rather than firing on any change
Details
- Feature Category: File Management
How It Works
- Choose a trigger: rules fire when a column changes, a column value changes to something specific, a new item is created, or an item is deleted
- Add conditions: for value-based triggers, pick the column, the comparison, and the value that should fire the rule
- Pick the recipient: the notification email goes to a person you name or to the person in a column on the item
- Notifications arrive by email: recipients get a message sent from no-reply@sharepointonline.com when the rule fires
- Manage in one place: each list shows its rules together, where they can be toggled on and off, edited, or deleted
Limits and Nuances
- 15 rules per list: each list or library supports a maximum of 15 rules
- Email is the action: rules send notifications; they do not update items, create items, or call other systems, which is where Power Automate picks up
- Recipients are internal: rule notifications go to people inside your organization
- Sender address: emails come from no-reply@sharepointonline.com, which is worth telling recipients so messages are not missed
- Permissions matter: creating and managing rules requires sufficient permissions on the list, while everyone else continues using the list normally
- Modern lists and libraries: rules are a Microsoft 365 feature of modern SharePoint lists and document libraries
Common Questions About Rules in SharePoint
What are rules in SharePoint lists and libraries?
Rules are simple, no-code automations attached to a list or library. Each rule pairs a trigger, such as a column value changing or a new item being created, with an email notification to a person you choose. They are built by completing a plain-language sentence, which makes them the fastest way to keep people informed about list activity.
What can trigger a rule?
Four triggers are available: a column changes, a column value changes to meet a condition you define, a new item is created, or an item is deleted. The condition-based trigger is the most powerful, since it fires only when a specific column reaches a specific value, such as Status changing to Approved or Priority changing to Critical.
Can a rule notify the person an item is assigned to?
Yes. The recipient of a rule’s notification can be a specific named person or the person stored in a column on the item, such as Assigned To or Created By. That makes handoff scenarios easy: when work moves to someone, the rule emails whoever the item points to at that moment rather than a fixed individual.
How many rules can I create on a list?
Each list or library supports up to 15 rules. In practice that is plenty for notification scenarios, since one well-built conditional rule often replaces several broad ones. If a process genuinely needs more triggers, branching logic, or actions beyond email, that is the signal to build the automation in Power Automate instead.
What is the difference between rules and Power Automate?
Rules cover one action, an email notification, triggered by changes within a single list, and they take under a minute to create. Power Automate handles multi-step flows: updating items, creating files, posting to Teams, requesting approvals, and connecting other systems. Start with rules for notifications and move to Power Automate when the process outgrows them.
Who should set up rules and notifications for our lists?
Rules are simple enough for list owners to manage themselves once the lists are designed well, with the right columns and choice values to trigger on. Greg Zelfond, the SharePoint consultant behind LookBook 365, builds lists, libraries, and entire intranets out of the box, structured so notifications and automation fall into place naturally.