
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
In Winter ’22, Salesforce discontinued the Run Flows permission for the Guest User and Experience Cloud External User profiles in new orgs. In Spring ’23, Salesforce removed Run Flows from the Guest User profile in all orgs.
It was possible to give this permission through profiles and permission sets until the update completed in the Spring of 2023. Since it is not possible to assign permission sets to guest users, it is not possible to give this permission through permission sets either. To allow guest users access your flows, you need to grant individual access to each flow that you want them to access.
Bid Farewell to Run Flows for Guest Users
Go to Guest User Profile → Run Flows.
If you don’t see “Run Flows” permission on the guest user profile, the release update is enforced.
When the release update is enforced to your sandbox or production org, new permissions need to be created for required users and allow access for every flow you want accessible to the guest user.
For more information see Allow Guest Users to Access Flows.
Note: When the admin user cannot see the option "Edit Access" on the Flow Setup page in the Lightning UI for an Autolaunched Flow, the workaround is to use the Classic UI and look for the "Security" link for the flow as instructed below and in the published Known Issue.
Note: All flows with Managed packaged flows will have an impact where you will not be able to make any changes or update the permissions for guest users to access flows. To make any changes please follow the workaround and work with the package provider as instructed below.
Known Issue - Unable to edit flows to provide Granular Permissions for Guest Users for Managed Package flows
000394651