Permission & Access Issues

How to Fix SharePoint Online Users Unable to Start a Workflow

Amos GikundaAmos Gikunda Nov 2, 2026 868 views

Question details

Specific group users with Edit permissions are unable to start workflows in SharePoint Online after a migration from SharePoint Server.

How to Fix SharePoint Online Users Unable to Start a Workflow
Product
SharePoint Online
Device & OS
not provided
Scenario
Attempting to trigger or start an existing SharePoint workflow post-migration.
Observed behavior
The workflow fails to execute for certain users, despite those users previously having no issues in SharePoint 2013 and currently showing as having Edit permissions.
Before you start

Ensure you have Site Administrator or Full Control privileges on the affected SharePoint site to check and modify user permissions.

Solution 1Recommended

Verify and Re-assign User Permissions

Check the actual permission levels of the affected users using the Check Permissions tool, and re-add them to the group to clear any caching or migration glitches.

During a migration from SharePoint Server (such as 2013) to SharePoint Online, user permission mapping can occasionally experience localized glitches. Even if a user appears in a group with Edit permissions, underlying caching issues may block their ability to trigger workflows.

1
Access advanced permissions

Navigate to 'Site settings', click on 'Site permissions', and then select 'Advanced permissions settings'.

2
Check exact user permissions

Click the 'Check Permissions' button on the ribbon. Enter the affected user's name or email to verify that they truly hold the 'Edit' permission level.

3
Remove and re-add the user

If the permission is correct but the workflow still fails, remove the affected users from the relevant SharePoint group. Save the changes, and then re-add the users back to the group.

Verify and Re-assign User Permissions
Permission Propagation Delay: Keep in mind that permission propagation or backend caching might delay the change. Wait a few minutes after re-adding the users before asking them to test the workflow again.
Free Microsoft Office alternative

Looking for a Lightweight Office Solution? Try WPS Office

While SharePoint and complex workflows require Microsoft infrastructure, you might be looking for a fast, free, and highly compatible alternative for your daily document management. WPS Office provides exceptional functionality without the heavy subscription costs.

  1. 1. Download the installer: Visit the official WPS Office website and download the free installation package.
  2. 2. Install the software: Run the installer on your Windows, Mac, or Linux device and follow the simple on-screen instructions.
  3. 3. Open your documents: Launch WPS Office and open your existing Microsoft Word, Excel, or PowerPoint files directly to start editing.
Fully compatible with Microsoft Office formats, including .docx, .xlsx, and .pptx.Lightweight architecture ensures fast installation and smooth performance on older hardware.Free to use with a familiar, tabbed user interface that eliminates the learning curve.Built-in PDF editing, merging, and format conversion tools.
microsoft office alternative - wps office

Frequently Asked Questions

Why can only specific users not start the SharePoint workflow?

This often happens after a migration from SharePoint Server to SharePoint Online due to localized permission caching glitches or orphaned user account mappings in specific site groups.

How can I accurately verify if a user has Edit permissions in SharePoint?

Go to 'Site settings' > 'Site permissions' > 'Advanced permissions settings', and use the 'Check Permissions' tool in the ribbon. Enter the user's email to see their exact permission levels across the site.

What should I do if removing and re-adding the user does not fix the workflow issue?

If the workflow still will not start after re-assigning permissions and waiting for the changes to propagate, test if the problem occurs on a newly created site. If the issue continues, contact your organization's IT administrator to open a support ticket with Microsoft regarding the migration.