It is possible to update the flow designer properties

[Rashida Banu]

Hi Team,

in the flow designer properties we have a option called "run as" with the options

1.system user

2.user who initiates session.

but it is possible to set for a specific user like if "it integrator" user needs to set as run as.

can anyone suggest me.

Regards,

Banu

[Raj_Esh]

Hi Rashida,

Theoretically,

The user who initiates a 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

I think the possibility is: You can make the flow runs by selecting the User who initiates the session, and for the user which you mentioned, you can add the role.

Hope it helps.

Thanks,

Raj

[Shakeel Shaik]

Hi @Rashida Banu 

Here you will find the Flow Designer Properties.

 

I don't think, we can add user here.

If my response is helpful, then Please mark as Correct Answer/Helpful.

Please check and let us know.

Thanks 🙂

Shakeel Shaik.

[OlaN]

Hi,

Simply by using the options in Flow designer this is not possible.
Either you run as the system, or as the user who initiated the Flow.

I can think of a workaround that you could try, if this is really required.

1. On your Flow, select to run as user.
2. Select the "Create code snippet" from the Flow.
3. Create a scheduled script execution that runs as the specific user as required.
4. Paste the Flow code snippet in the script field of the scheduled script execution.
5. Run the scheduled script.