---
title: "Winter '26 Release: New Restrictions on Flow Access and User Permissions"
canonical: "https://help.fieldbuddy.com/space/FBDOCS/blog/6415089667/Winter%20'26%20Release%3A%20New%20Restrictions%20on%20Flow%20Access%20and%20User%20Permissions"
format: markdown
---
> ⚠️ Summary: Starting **Winter ’26**, Salesforce will enforce **“Restrict User Access to Run Flows.”**  
> ⚠️ Users must have the permissions to Run Flows assigned via Profile/Permission Set (and the access to flow. This is applicable Screen/Autolaunched flows.

Salesforce have been recently working into improvement of platform security, and the **Winter ’26 release** adds new restrictions on Flow access. This means users (or external guests) will need explicit permission to run specific flows.

### What is changing

From Winter' 26, Salesforce restricts a user’s ability to run a flow. A user must be granted the correct profile or permission set to run the flow. That can be granted either via assigning a permission **‘Run Flows’** on Profile level or Permission set level. 

![image-20251008-093832.png](media://1d0a5cb8-f1c2-496b-b522-496eaed29c81)

More detailed description of the changes (from Salesforce documentation)

- **No more implicit access:** Previously, all the users could run active screen or autolaunched flows,
- **FlowSites and guest access deprecation:** Public flows exposed via Sites or Experience Cloud guest users will be restricted unless specifically granted access.
- **Explicit permission now mandatory:** A user must have the **“Run Flows”** permission *and* be granted access to the individual flow — either via profile, permission set, or managed access list (only if `Override default behavior and restrict access to enabled profiles or permission sets.` is set on Flow itself)
- **Apex interactions affected:** If a flow calls Apex classes, users might also need permission to invoke those classes.

For FieldBuddy customers, the profiles **System Administrator, FieldBuddy Admin and Back Office** for the environments created in last 5 years have this permission checked (Run Flows).

### Which Flows are impacted

In the official salesforce FAQ following table is stated

|  |  |
| --- | --- |
| Impacted Flow Types: | Unaffected Flow Types: |
| Screen Flow<br>Autolaunched Flow<br>Recommendation Strategy<br>Field Service Mobile Flow<br>Contact Request Flow<br>Appointments Flow<br>FieldServiceWeb Flow (screen used in Appointments) | Record Triggered Flows<br>Scheduled Triggered Flows<br>PE Triggered Flows<br>Surveys<br>CustomEvent (Process Builder PE trigger)<br>InvocableProcess<br>Login Flows |

### What to do in case of Issues

If certain non-admin users are unable to to run the flow, it is necessary to make sure that there is a permission “Run Flows” granted for a user either via profile level of permissionset level. 

It is possible by opening a User, clicking on a Profile,  opening App permissions and check Run Flows checkbox, as on screenshot above.

In case if more granular control control is needed (so only share some of the flows to particular users) - then this [guide](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_security.htm&type=5) by can be handy.

### Useful Links

- Salesforce FAQ: [https://help.salesforce.com/s/articleView?id=001930084&type=1](https://help.salesforce.com/s/articleView?id=001930084&type=1)
- Salesforce Release Update: [https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update_restrict_user_access.htm&release=246&type=5](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update_restrict_user_access.htm&release=246&type=5)
- Limit User Access to Execute Flows - [https://help.salesforce.com/s/articleView?id=platform.flow_distribute_security.htm&type=5](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_security.htm&type=5)