Run as Property in flow designer

Ankita Gupte · ‎09-22-2020

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?

Willem · ‎09-22-2020

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...

View solution in original post

Ankita Gupte · ‎09-23-2020

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

Willem · ‎09-23-2020

Yes, so try limit running Flows as system as much as you can. But sometimes it is needed and handy that the option is there.

Test the Flow carefully and then publish it.