Controlling automation in your document libraries prevents unnecessary notifications and keeps your team focused on relevant updates. Learning exactly apply SharePoint Library Rules to Selected Files and Folders allows you to bypass the default behavior where rules trigger for every single document in a repository. By leveraging native metadata filters and Power Automate workflows, you can execute targeted actions like sending emails or updating statuses only when specific items are modified or selected.
Using Conditional Metadata to Target Specific Files
When determining apply SharePoint Library Rules to Selected Files and Folders, the most accessible method relies on native conditional columns. SharePoint's default "Rules" feature automatically applies to the entire library. To isolate specific files, you must create a dedicated metadata column that acts as a trigger, ensuring the rule only fires when you manually tag a selected file.
Follow these steps to configure a conditional rule using metadata:
- Navigate to your SharePoint document library and click + Add column at the end of your header row.
- Select Choice, name the column "Trigger Rule", add a choice named "Active", and click Save.
- Select a file in your library, open the details pane, and ensure the "Trigger Rule" column is empty by default.
- On the main library command bar, click Automate, select Rules, and click Create a rule.
- Choose the condition A column changes.
- Configure the logic sequence: Choose the column Trigger Rule, set the condition to is, and select the value Active.
- Define your action, such as Send email to, select the recipient, and click Create.
To verify this workflow, select a specific file in your library, change its "Trigger Rule" column to "Active", and confirm that the target email address receives the notification. Files left empty will not trigger the rule.
Building a Power Automate Flow for Selected Files
For a highly interactive approach to apply SharePoint Library Rules to Selected Files and Folders, you must utilize Power Automate. The native rules interface does not support a "run on demand" button for individual files. Creating an instant cloud flow provides a dedicated button in the SharePoint menu for any file you highlight.
Set up the on-demand flow by executing these steps:
- Go to make.powerautomate.com, click Create in the left sidebar, and select Instant cloud flow.
- Name your flow, check the box for the trigger For a selected file (SharePoint), and click Create.
- In the flow designer, select your specific Site Address and Library Name from the dropdown menus.
- Click New step, search for SharePoint, and select the Get file properties action to retrieve the file's metadata. Map the Id field to the dynamic content "ID" from your trigger.
- Click New step again to define your rule's action. For example, add Update file properties to change a status column, or Send an email (V2) to notify a manager.
- Click Save in the top right corner.
To test this configuration, return to your SharePoint library and select a single file. Click the three vertical dots (...) next to the file name, hover over Automate, and click the name of the flow you just created. Click Run flow in the right-hand panel and verify the action completes successfully.
Applying Workflows to Specific Folders Using Conditions

While investigating apply SharePoint Library Rules to Selected Files and Folders, you will find that isolating a specific folder requires evaluating the file path. Neither native rules nor the "selected file" trigger automatically restrict background automation to a single folder. You must build an automated flow that intercepts all library changes but immediately terminates if the item is not inside your target folder.
Configure a folder-specific rule with these instructions:
- In Power Automate, click Create and select Automated cloud flow.
- Choose the trigger When a file is created or modified (properties only) and connect your site and library.
- Click New step, search for Condition, and select the built-in Control action.
- In the first condition field, select the dynamic content Folder path.
- Change the operator dropdown from "is equal to" to contains.
- In the final field, type the exact name of your target folder surrounded by forward slashes (e.g., /Contracts/).
- Inside the If yes branch, add your desired rule actions (like sending an approval request). Leave the If no branch completely blank.
Verify this by uploading one document to the root library and another document into the "Contracts" folder. Check your flow's run history to ensure the rule only executed its actions for the document placed inside the designated folder.
Managing Document Preparation with WPS Office

Your local software stack indirectly influences apply SharePoint Library Rules to Selected Files and Folders by dictating how documents are formatted and tagged before they enter the cloud environment. WPS Office cannot alter Microsoft SharePoint server settings, user permissions, or Power Automate triggers. Those mechanics are strictly controlled by your Microsoft 365 tenant. However, WPS Office can streamline the process of finalizing files before you upload them into a strictly regulated SharePoint folder.
If your SharePoint folder rule automatically sends files for executive review upon upload, the documents must be correctly formatted beforehand. You can use WPS Office to prepare these files locally:
- Open your draft in WPS Writer or WPS Spreadsheet.
- Finalize your formatting, ensuring headers and tables are locked.
- Use the built-in PDF tool by clicking Export to PDF in the toolbar to prevent further editing.
- Save the finalized PDF to your local drive.
- Open your web browser, navigate to your SharePoint library, and drag the PDF directly into the specific folder that triggers your Power Automate condition.
Frequently Asked Questions
Can I trigger a SharePoint rule by selecting multiple files at once?
Native SharePoint rules do not trigger based on selection; they trigger on metadata changes, which you can apply in bulk using the "Edit in grid view" feature. However, the Power Automate "For a selected file" trigger only processes a single file per execution. If you select multiple files in the SharePoint interface, the Automate menu will disable custom flows. To process multiple files, you must use a scheduled flow that queries the library for files matching a specific status.
Why does my folder path condition fail in Power Automate?
Folder path conditions usually fail due to incorrect text matching. The dynamic content for "Folder path" in SharePoint includes forward slashes and the library name. If your library is named "Shared Documents" and your folder is "Invoices", the path outputs as "/Shared Documents/Invoices/". Using the "is equal to" operator will fail if you only type "Invoices". Always use the "contains" operator and format your text as "/Invoices/" to ensure accurate matching.
Do I need administrator permissions to create flows for selected files?
You do not need full SharePoint administrator privileges, but you do need "Edit" permissions on the specific document library to add flows to the Automate menu. Additionally, your Microsoft 365 account must have an active Power Automate license. If you only have "Read" access, the Automate menu will not allow you to configure new rules or attach instant flows.
Does modifying a file locally affect SharePoint conditional rules?
No. while working on apply SharePoint Library Rules to Selected Files and Folders, recognize that SharePoint only registers changes made within its own ecosystem or synced via OneDrive. Editing a document locally offline will not trigger any SharePoint rules. The rule will only fire once you upload the modified file back to the SharePoint library and overwrite the existing version, which registers as a "modified" event in the system.




