Run as Property in flow designer

[Ankita Gupte]

There is Run As point in properties of flow designer which has two options User who initiates the session and system user. I want to know when to use which option and Why?

 

[Viraj Hudlikar]

Hi Ankita,

Please find LINK to understand more on this.

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.

Thanks & Regards,
Viraj Hudlikar

[Ashutosh Munot1]

Hi,

It depends on your requirement. If you want only specific users to run that flow then it will use current user session and evaluate all the ACL on the tables or action or activities in that flow.

If you use system user it has access to all the objects.

So i would say go for system user now. In Paris we will get a option to select specific roles as well.

Thanks,
Ashutosh

[Willem · Accepted solution]

User who initiates session

Select the user who initiates the session option when updates should come from the user who triggered the flow. For example, when you want incident record comments to come from the current user, or approval emails to originate from the approver. Run As settings for a flow don't apply to child subflows. When flows run as the user who initiates the session, the system limits flow actions by user ACL restrictions. Ensure that security restrictions don't prevent users who trigger the flow from performing flow actions. Flows run by the initiating user also respect user-specific settings such as date/time formats.

System user

• Runs as System
  
• Updates appear as done by System
• Does not evaluate Users roles/access when running the Flow

Also refer to:

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/administer/flow-designer/task/cr...

[Ankita Gupte]

So the user who does not have admin role can run the flow designer which Run as option as system user?