Notes
In the context of Salesforce and Flow Builder, the "running user" refers to the user context under which an automated process or flow is executed. When a flow is triggered, it can run under the permissions and access rights of either the user who initiated the flow (the "running user") or a designated "system user."
Here's a brief explanation of the two types of running users:
-
Running User: When a flow runs with the "running user" context, it means the flow executes with the permissions and access rights of the user who triggered or initiated the flow. This includes their profile permissions, record access, and field-level security. Essentially, the flow behaves as if the actual user is performing the actions defined within the flow.
-
System Context (System Mode): Alternatively, a flow can run in the "system context," which means it executes with elevated permissions similar to a system administrator. This is also known as "system mode" or "without sharing" mode. In this mode, the flow bypasses the user's individual permissions and operates based on the system's permissions, allowing it to access and modify records that the running user might not have access to otherwise.
The choice between running the flow with the "running user" or in "system context" depends on the specific requirements of the automation process. If the flow needs to act based on individual user permissions and data access, using the "running user" context is appropriate. However, if the flow needs to perform actions that require elevated privileges, such as updating records owned by other users or modifying records with restricted access, running the flow in "system context" may be necessary.
When creating flows in Flow Builder, you can specify the running user context based on the business needs. It's important to carefully consider the security implications and potential data access concerns when choosing the appropriate running user context for your flows. Always ensure that automated processes adhere to your organization's security and compliance policies.
